I wonder what is different in booting the kernel from loader(8) and from
boot2.
In vmware2 I am not able to boot the kernel from boot2, it hangs after
loading the kernelfile. Using loader it goes fine.
I tried current,stable and generic kernels, all without luck.
This was not really a problem, u
David O'Brien wrote:
> You quite speak for yourself. I've seen the FreeBSD community more split
> 50%-50% in their love-hate of Vinum. Many of us still use ccd(4) because
> Vinum did not meet our needs.
Alfred Perlsteing claims "Vinum comes from the universe where Spock
has a beard" (sorry, Gre
On Wed, May 29, 2002 at 02:18:40PM -0500, Brandon D. Valentine wrote:
> If you really want to play with RAIDframe I'd guess you'll have a much
> easier time of it under NetBSD, where it is included with the operating
> system. Getting it working under FreeBSD could be a lot of fun and you
> might
I have this problem, someone can help me?
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x3090
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01d0a61
stack pointer = 0x10:0xd7ec3e18
frame pointer = 0x10:0
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/39125 presents an
interesting hypothesis, namely that vidcontrol -m ought to be enabled by
default in usbd.conf. I tend to agree with that premise, but before I
commit it I was curious as to what the "cost" of doing this would be.
Specifically, I hav
Hi,
kern_exit.c:wait1() has the following lines in -STABLE:
> if ((p->p_sigparent != SIGCHLD) ^ ((uap->options & WLINUXCLONE) != 0))
> continue;
As it is, if you ptrace(PT_ATTACH) to a process started with
rfork(flags|RFLINUXTHPN), and do a waitpid() as you normally would, this
causes
--- Andy Sporner <[EMAIL PROTECTED]> wrote:
> My fault. I am using 5.0
> man shutdown_kproc
Ok, I cant find any man page called shutdown_kproc in either 4.3 or 4.4.
Anyway, he wants to destroy a "thread", and not an "internal" daemon/process.
To destroy a kernel thread, you need to make use of
On Sun, Jun 09, 2002 at 11:40:09PM -0700, Terry Lambert wrote:
> 0xdeadc162 - 0xdeadc0de = 0x0084 = 132 decimal
>
> Look for a short value that's getting set to 132.
As I said in another email, I think this is td1->td_priority in
kern_mutex.c:510.
-Arun
To Unsubscribe: send mail t
Andy Sporner wrote:
>
> man ktread_shutdown
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
I can't find any man pages about it; I searched on the net, grep'ed
/usr/src entirely but any results.
I've freebsd 4.6RC release.
Any a
My fault. I am using 5.0
Try this:
man shutdown_kproc
There was some name changes as shown:
HISTORY
The kproc_start() function first appeared in FreeBSD 2.2. The
kproc_shutdown(), kthread_create(), kthread_exit(), kthread_resume(),
kthread_suspend(), and kthread_suspend_check(
á¹Ð¹Óâ»Ãá¡ÃÁ¤Çº¤ØÁ¹éÓ˹ѡ à¾ÔèÁ¹éÓ˹ѡ ÃÑ¡ÉÒÊØ¢ÀÒ¾
¤Ø³ËÃ×ͤ¹·Õè¤Ø³ÃÑ¡¡ÓÅѧÁͧËÒÇÔ¸Õ´ÙáÅÊØ¢ÀÒ¾·Õèà»ç¹¸ÃÃÁªÒµÔÍÂÙèãªèäËÁ?
ËÒ¡¤Ø³àº×èÍ˹èÒ¡Ѻ¤ÇÒÁ¾ÂÒÂÒÁ·ÕèäÁè»ÃÐʺ¤ÇÒÁÊÓàÃ稤ÃÑé§áÅéǤÃÑé§àÅèÒ
㹡ÒôÙáÅÊØ¢ÀÒ¾à¾×èÍÃÙ»ÃèÒ§·Õè´Õ àÃÒÁÕâ»Ãá¡ÃÁâÀª¹Ò¡ÒÃà¾×èÍÊØ¢ÀÒ¾ ·ÕèªèǤسä´é
ÊÓËÃѺ¼Ùé·ÕèÁÕ»ÑËÒ ¹éÓ˹ѡà
Ferruccio Vitale wrote:
>Hi,
>
>how can I destroy a kernel thread that I previously created?
>Regards,
>
>Ferruccio
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-hackers" in the body of the message
>
>
man ktread_shutdown
To Unsubscribe: send mail to [EMAIL PR
Hi,
how can I destroy a kernel thread that I previously created?
Regards,
Ferruccio
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Frank Mayhar wrote:
>
> I'm experiencing hangs as well. At first I thought it was the fxp0/sym
> driver thing, but I've since changed hardware almost completely and the
> hangs persis. I'm now strongly suspecting some kind of interrupt problem.
> For the record, I've attached my dmesg output.
> The cardreader is another story. I'm free in choosing one which I can get to
> work. Does anyone have any experience with these things under FreeBSD? Any
> brands/types from which I *really* should stay away?
I've used a wide range of serial port ones; most seem OEM-ed IBMs or
SEMA/Schulber
Hi there -
One of my clients would like me to hack together an application involving a
cardreader and a touchscreen. How would I deal with these two rather 'odd'
pieces of hardware. I didn't have any say in the purchasing of the
touchscreen, but I suppose that shouldn't give me any trouble? It
16 matches
Mail list logo
