Re: kernel panic at boot on any 6.x OS
It looks as if you've hit a device driver that is trying to print out a null string. The message you've given doesn't provide any more information than that. If you install a snapshot kernel it will probably have ddb compiled in which will allow you to at least get a backtrace. I'm sorry you're having trouble. -Kip On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote: Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Progress on scaling of FreeBSD on 8 CPU systems
On Sun, 25 Feb 2007, Kris Kennaway wrote: On Sat, Feb 24, 2007 at 10:00:35PM -0700, Coleman Kane wrote: What does the performance curve look like for the in-CVS 7-CURRENT tree with 4BSD or ULE ? How do those stand up against the Linux SMP scheduler for scalability. It would be nice to see the comparison displayed to see what the performance improvements of the aforementioned patch were realized to. This would likely be a nice graphics for the SMPng project page, BTW... There are graphs of this on Jeff's blog, referenced in that URL. Fixing filedesc locking makes a HUGE difference. I think the real message of all this is that our locking strategy is basically pretty reasonable for the paths exercised by this (and quite a few) workloads, but our low-level scheduler and locking primitives need a lot of refinement. The next step here is to look at the impact of these changes (individually and together) with other hardware configurations and other workloads. On the hardware side, I'd very much like to see measurements done on that rather nasty generation of Intel Xeon P4's where the costs of mutexes were astronomically out of proportion with other operation costs, which historically has heavily pessimized ULE due to the additional locking it had (don't know if this still applies). It would be really great if we could find workload owners who would maintain easy-to-run benchmark configurations and also run them regularly on a fixed hardware configuration over a long time publishing results and testing patches. Kris has done this for SQL benchmarks to great effect, giving a nice controlled testing environment for a host of performance-related patches, but SQL is not the be-all and end-all of application workloads, so having others do similar things with other benchmarks would be very helpful. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can only have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime: 36s
cannot dump. No dump device defined
automatic reboot in 15 seconds
This problem does not occur within any 5.x OS for me. I would
certainly like to resolve this issue now, but this sort of debugging
is over my head beyond running fsck (which I've tried). Any ideas here?
Thanks in advance for your help!
---
Joe Auty
NetMusician: web publishing software for musicians
http://www.netmusician.org
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Daan
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Progress on scaling of FreeBSD on 8 CPU systems
On Feb 25, 2007, at 12:41 AM, Kris Kennaway wrote: On Sat, Feb 24, 2007 at 10:00:35PM -0700, Coleman Kane wrote: What does the performance curve look like for the in-CVS 7-CURRENT tree with 4BSD or ULE ? How do those stand up against the Linux SMP scheduler for scalability. It would be nice to see the comparison displayed to see what the performance improvements of the aforementioned patch were realized to. This would likely be a nice graphics for the SMPng project page, BTW... There are graphs of this on Jeff's blog, referenced in that URL. Fixing filedesc locking makes a HUGE difference. Kris, This is fantastic news! Is there an approximate date for when all of these patches are going to hit CVS? Keep up the great work! :) Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Progress on scaling of FreeBSD on 8 CPU systems
On Sun, 25 Feb 2007, Martin Blapp wrote: It would be really great if we could find workload owners who would maintain easy-to-run benchmark configurations and also run them regularly on a fixed hardware configuration over a long time publishing results and testing patches. Kris has done this for SQL benchmarks to great effect, I'm interested in such a workload test. At my job we run various other servers which have a classic virus/antispam environment. And unfortunatly clamd behaves not very well on FreeBSD (see mails to freebsd-threads), and this happens even on 2-CPU systems. I think its not very difficult to make a scripted load test, with 2/4/6/8/16/32 scans in parallel, with ULE or BSD scheduler. As long as it is realistic and reproduceable, it sounds good to me. Btw: what is the best method to profile a threaded application to see where it spends the most CPU time ? Try looking at system pmc support -- using system pmcs, you can profile a variety of factors (including CPU use, cache misses, etc) across the whole system (kernel and application), so it's a really neat tool. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can only
have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong
version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
# diff 6.x GENERIC
19c19
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPDIVERT
#options VFS_AIO
#options HZ=1200
#options SMP # Symmetric MultiProcessor
Kernel
#device pf
#device pflog
#device pfsync
options COMPAT_LINUX
options BRIDGE
- ---
makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
# Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
options LINPROCFS
#makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
#options SCHED_ULE # ULE scheduler
77,80d58
options AHC_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in
debug
# output. Adds ~215k to driver.
103a82,83
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
104a85,86
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
226a209
devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
devicewlan_wep# 802.11 WEP support
devicewlan_ccmp # 802.11 CCMP support
devicewlan_tkip # 802.11 TKIP support
249a236,238
deviceath # Atheros pci/cardbus NIC's
deviceath_hal # Atheros HAL (Hardware
Access Layer)
deviceath_rate_sample # SampleRate tx rate control
for ath
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release, but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime: 36s
cannot dump. No dump device defined
automatic reboot in 15 seconds
This problem does not occur within any 5.x OS for me. I would
certainly like to resolve this issue now, but this sort of debugging
is over my head beyond running fsck (which I've tried). Any ideas
here?
Thanks in advance for your help!
---
Joe Auty
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Kip, I'd gladly try a snapshot kernel, but I'm not sure which one to pick out of this list: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/kernels Any suggestions? On Feb 25, 2007, at 2:59 AM, Kip Macy wrote: It looks as if you've hit a device driver that is trying to print out a null string. The message you've given doesn't provide any more information than that. If you install a snapshot kernel it will probably have ddb compiled in which will allow you to at least get a backtrace. I'm sorry you're having trouble. -Kip On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote: Hello, (sorry, don't know whether kernel problems should go to questions or hackers, or both).. This has been a long-standing problem of mine, but I always ignored it hoping it would go away on its own with a future 6.x release, but it remains... No matter whether I boot into safe mode or regular mode, with all kernel extensions disabled in /boot/loader.conf, I get the following panic late at boot of a fresh RELENG_6_2 kernel (with only a few services left to bring up). The 6.x kernels I've tried all build and installed cleanly without any errors... WARNING: Device driver Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06d4614 stack pointer = 0x28:0xf015491c frame pointer = 0x28:0xf015491c code segment = base 0x0, limit 0xff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 898 (kldload) trap number = 12 panic: page fault uptime: 36s cannot dump. No dump device defined automatic reboot in 15 seconds This problem does not occur within any 5.x OS for me. I would certainly like to resolve this issue now, but this sort of debugging is over my head beyond running fsck (which I've tried). Any ideas here? Thanks in advance for your help! --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4bZMCgdfeCwsL5ERAv0zAJ4zRjih+XoXGjF8Bc4hd2Yj7I0WNQCfeEb5 5mLoo1jTuYnJpa2z1EJqbUY= =Jwsg -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 11:14 AM, Joe Auty wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print
out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're having trouble.
Grepping the source tree on 6.2-RELEASE shows this message can
only have com
from one place : sys/kern/kern_conf.c in the function prep_cdevsw() :
if (devsw-d_version != D_VERSION_01) {
printf(
WARNING: Device driver \%s\ has wrong
version %s\n,
devsw-d_name == NULL ? ??? : devsw-d_name,
and is disabled. Recompile KLD module.);
Looks like the kernel and the modules are out of sync.
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=myconfig
Shouldn't this have installed a fresh kernel plus only essential
modules?
Here is a diff of my kernel config (which I've called, rather
uncreatively, 6.x) against GENERIC:
nothing unusual, just IPFIREWALL and Linux compat stuff, right?
Forgot to add that I believe I've also tried building a GENERIC
kernel and ran into this same problem. It's been a while since I
tried this though, so I'll gladly try this again if you think it
would be a useful test! =)
# diff 6.x GENERIC
19c19
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.7.2.2 2006/05/01
00:15:12 scottl Exp $
- ---
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.13 2006/10/09
18:41:36 simon Exp $
30,42c30
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPDIVERT
#options VFS_AIO
#options HZ=1200
#options SMP # Symmetric
MultiProcessor Kernel
#device pf
#device pflog
#device pfsync
options COMPAT_LINUX
options BRIDGE
- ---
makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
44,49d31
# Enable the linux-like proc filesystem support (requires
COMPAT_LINUX and PSEUDOFS)
options LINPROCFS
#makeoptions DEBUG=-g# Build kernel with gdb(1)
debug symbols
#options SCHED_ULE # ULE scheduler
77,80d58
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
103a82,83
options AHC_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~128k to
driver.
104a85,86
options AHD_REG_PRETTY_PRINT# Print register bitfields
in debug
# output. Adds ~215k to
driver.
226a209
devicestge# Sundance/Tamarack TC9021
gigabit Ethernet
248a232,234
devicewlan_wep# 802.11 WEP support
devicewlan_ccmp # 802.11 CCMP support
devicewlan_tkip # 802.11 TKIP support
249a236,238
deviceath # Atheros pci/cardbus NIC's
deviceath_hal # Atheros HAL (Hardware
Access Layer)
deviceath_rate_sample # SampleRate tx rate
control for ath
On 2/24/07, Joe Auty [EMAIL PROTECTED] wrote:
Hello,
(sorry, don't know whether kernel problems should go to
questions or
hackers, or both)..
This has been a long-standing problem of mine, but I always ignored
it hoping it would go away on its own with a future 6.x release,
but
it remains...
No matter whether I boot into safe mode or regular mode, with all
kernel extensions disabled in /boot/loader.conf, I get the
following
panic late at boot of a fresh RELENG_6_2 kernel (with only a few
services left to bring up). The 6.x kernels I've tried all build
and
installed cleanly without any errors...
WARNING: Device driver
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x40
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06d4614
stack pointer = 0x28:0xf015491c
frame pointer = 0x28:0xf015491c
code segment = base 0x0, limit 0xff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interupt enabled, resume, IOPL = 0
current process = 898 (kldload)
trap number = 12
panic: page fault
uptime:
Re: Progress on scaling of FreeBSD on 8 CPU systems
On Sun, Feb 25, 2007 at 01:54:20PM +0100, Martin Blapp wrote: Hi, It would be really great if we could find workload owners who would maintain easy-to-run benchmark configurations and also run them regularly on a fixed hardware configuration over a long time publishing results and testing patches. Kris has done this for SQL benchmarks to great effect, I'm interested in such a workload test. At my job we run various other servers which have a classic virus/antispam environment. And unfortunatly clamd behaves not very well on FreeBSD (see mails to freebsd-threads), and this happens even on 2-CPU systems. I think its not very difficult to make a scripted load test, with 2/4/6/8/16/32 scans in parallel, with ULE or BSD scheduler. Btw: what is the best method to profile a threaded application to see where it spends the most CPU time ? If you can package up some kind of test or analogous workload that I can run, I'd be happy to take a look at profiling it on MP hardware. Kris P.S. I assume you've done all the usual things like using libthr instead of libpthread. pgpeplqBKeDHu.pgp Description: PGP signature
Re: Progress on scaling of FreeBSD on 8 CPU systems
Hi, It would be really great if we could find workload owners who would maintain easy-to-run benchmark configurations and also run them regularly on a fixed hardware configuration over a long time publishing results and testing patches. Kris has done this for SQL benchmarks to great effect, I'm interested in such a workload test. At my job we run various other servers which have a classic virus/antispam environment. And unfortunatly clamd behaves not very well on FreeBSD (see mails to freebsd-threads), and this happens even on 2-CPU systems. I think its not very difficult to make a scripted load test, with 2/4/6/8/16/32 scans in parallel, with ULE or BSD scheduler. Btw: what is the best method to profile a threaded application to see where it spends the most CPU time ? Martin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Progress on scaling of FreeBSD on 8 CPU systems
On Mon, Feb 26, 2007 at 12:27:01AM +0100, Martin Blapp wrote: Hi, If you can package up some kind of test or analogous workload that I can run, I'd be happy to take a look at profiling it on MP hardware. Should be possible. Btw. Has setting kern.threads.virtual_cpu to a different value effect for running programms or just started ones ? Dunno what that does, sorry. P.S. I assume you've done all the usual things like using libthr instead of libpthread. Yes, all clamd installations we have run with libthr, since libptread is completly unusable and libc_r has small hangs from time to time. The question is just if this is a clamd problem or an threading library problem. OK Kris pgp4DUPuZPz4x.pgp Description: PGP signature
the new functions of the crunchgen
Hi,
Crunchgen is a smart tools to create a tiny bsd. I've used it for
years.
Sometime, we need some scripts to help crunchgen to generate the makefile
when we combine some foreign packages. If not, the make will stop because of
the definition the symbols. So I modified the codes.
1. Add two options to special command
special progname nlib library-file-name
enter the home directory of the library, run make to rebuild the
static library,
and tell the 'ld' to add this library to the progname.lo.
special progname slib library-file-name
like nlib, except that the library will be linked as a single
file.
2. Add make xxx || echo Never mind. to meet some Makefiles
3. Disable adding the underscore ('_') to the symbols
see the attachment for detail.
Paul.
crunchgen.patch
Description: Binary data
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Progress on scaling of FreeBSD on 8 CPU systems
Hi, If you can package up some kind of test or analogous workload that I can run, I'd be happy to take a look at profiling it on MP hardware. Should be possible. Btw. Has setting kern.threads.virtual_cpu to a different value effect for running programms or just started ones ? P.S. I assume you've done all the usual things like using libthr instead of libpthread. Yes, all clamd installations we have run with libthr, since libptread is completly unusable and libc_r has small hangs from time to time. The question is just if this is a clamd problem or an threading library problem. -- Martin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sil3124 sata
Just wondering if there is any planned support for this card (or similar) I've added sos@ to Cc list, who may have interest to this as well. Note that developing drivers requires that the developer has his hands on actual hardware and hardware specifications. Exactly, get me the HW on my lab table and I'll do the driver as time/docs permits, its that simple :) -Soren Is getting a sil3124 board on Soren's lab table a job for the FreeBSD Foundation? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
- Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. Ted ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sil3124 sata
On Sun, Feb 25, 2007 at 08:15:13PM +, Dieter wrote.. Just wondering if there is any planned support for this card (or similar) I've added sos@ to Cc list, who may have interest to this as well. Note that developing drivers requires that the developer has his hands on actual hardware and hardware specifications. Exactly, get me the HW on my lab table and I'll do the driver as time/docs permits, its that simple :) -Soren Is getting a sil3124 board on Soren's lab table a job for the FreeBSD Foundation? Not necessarily, no. Soren often gets equipment donated by hardware vendors or from whoever else feels something needs to be supported . That includes private individuals. Wilko -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: - Original Message - From: Joe Auty [EMAIL PROTECTED] To: Daan Vreeken [PA4DAN] [EMAIL PROTECTED] Cc: Kip Macy [EMAIL PROTECTED]; freebsd-questions@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, February 25, 2007 8:14 AM Subject: Re: kernel panic at boot on any 6.x OS Any idea how this could have happened after disabling everything in my /etc/loader.conf, and simply running a: make buildworld make buildkernel KERNCONF=myconfig make installkernel KERNCONF=myconfig well your supposed to do this single-user, run mergemaster and a few other things. I also don't see a make installworld. I usually perform those steps after I've rebooted to ensure that my system will boot off the new kernel, as per the instructions in the FreeBSD handbook. Joe, please try booting from a 6.2-release install ISO. If it works without panicing, then you did something wrong during the upgrade. Downloading the image now, I'll let you know if I'm able to boot from it... Since by your own admission your not an expert, you would be well advised to simply back up your files the old fashioned way, reformat your hard disk, install from a 6.2 boot ISO, then restore your files. Leave the fancy in-place updating to someone else. It's a big PIA and doesen't work half the time anyway. How well does simply upgrading with the CD work (as opposed to wiping clean)? I've upgraded several times to new releases simply by rebuilding world, it has never failed me in the past. I don't doubt what you are saying here, but since I will have to change how I work, assuming that I can boot off of the 6.2 CD, I'd appreciate any general upgrade tips that don't involve wiping the disk clean (which is not really an option). For instance, is rebuilding world between point releases (e.g. 5.4 to 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)? I'll do my own homework regarding this too, but I appreciate any nuggets of wisdom you might have! As far as me being an expert, I guess I'd categorize me somewhere in between complete newb and FreeBSD developer =) Thanks again! - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4oC3CgdfeCwsL5ERAj3vAJ9bMYSj33hg/jU5jU6RyIjXqJ/YLwCfVumh FsunyXJGMjXHEHKso7xWzcI= =0p6j -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
