In message <[EMAIL PROTECTED]> Jose Gabriel J Marcelino writes:
: db> trace
: pccard_scan_cis(c1082680,c0167e0c,c9f43e88,0,0) at pccard_scan_cis+0x120
: pccard_read_cis(c1091a00) at pccard_read_cis+0xa9
: pccard_attach_card(c1082680) at pccard_attach_card+0xc5
: pccbb_insert(c1091c00,c9f43fa8,c109
In message <[EMAIL PROTECTED]> Jose Gabriel J Marcelino writes:
: Ok, some people tried to help me find out why does the Aironet driver
: panic on reinsertion, under NEWCARD with my recent patch (see previous
: message and PR) however I need additional help to find the problem.
*ALL* cards panic
I don't recall reports of trouble with recent CURRENT, but my CVSup
from yesterday afternoon is panicing. Before I try too debug this, has
anyone been getting these or knows what I might be missing?
Boot messages and the panic info are attached.
--
Crist J. Clark [EMAIL
Latest -CURRENT buidkernel died with this error messages:
===> sound/driver
===> sound/driver/ad1816
rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o snd_ad1816.ko snd_ad1816.kld
ad1816.o @ machine symb.tmp tmp.o bus_if.h device_if.h isa_if.h pci_if.h ac97_if.h
channel_if.h feeder_if.h m
Argl, the correct URL is of course:
http://www.attic.ch:80/patches/rpc.diff_04022001.sh.tgz
Cheers:
Martin
Martin Blapp, [EMAIL PROTECTED]
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +4
Hi,
So, I have merged in the newest libc changes and fixed some
buildworld issues. It still needs some _THREAD_SAFE fixes I
guess, cause we build now thread-safe libc per default. But
we can do this later ...
Go into your CURRENT source tree and execute the shell archive,
it will create the nec
Hi again,
Ok, some people tried to help me find out why does the Aironet driver
panic on reinsertion, under NEWCARD with my recent patch (see previous
message and PR) however I need additional help to find the problem.
I'm including the complete details on the events leading to the panic.
My k
Szilveszter Adam wrote:
>
> On Sun, Feb 04, 2001 at 02:03:22AM -0800, Doug Barton wrote:
> > FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but
> > there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X
> > libraries in the directory, although I'm not sure wha
Cher Mr ou Mme.
Nous vous prions de bien vouloir trouver ci-dessous
une information concernant les adresses électroniques concernant les
disciplines suivantes.
Médecins généralistes et
spécialistes-kinésithérapeutes-homéopathes-gynécologues-rhumatologues-pneumo
logues-gastro-entérologues-psychiatr
Hi,
Replying to myself. Seeing no answers I decided to work a little on adding
the NEWCARD support to an(4) and I'm now sending this using it :-)
It works ok, but card reinsertions cause at least this notebook to panic.
I've submitted a PR with the appropriate patches. It's online at:
http://ww
On Sun, 4 Feb 2001, Andrzej Bialecki wrote:
> According to procfs(5), the status line contains several well-defined
> fields separated by spaces. However, the kernel thread names look like
> 'swi5: task queue' and 'swi1: net', which results in variable number of
> space-separated fields. As a con
Hi,
Whoever made procfs aware of kernel threads broke also the
/proc/%pid/status line. Or, maybe it's a by-product of showing
kthreads in the proc table...
According to procfs(5), the status line contains several well-defined
fields separated by spaces. However, the kernel thread names look like
Recently, I updated a box with an ISA Advansys controller card + HP CD
Burner to -CURRENT. On doing so, I discovered that my machine crashed at
boot due to a NULL pointer passed to free(). John Baldwin provided me
with a set of patches that appears to correct bugs in the Advansys (adv)
driver t
It's normal. bpf implements what I currently have for my
preferred way of preventing a DoS with cloning devices.
The message indicates that the bpf0 device node were reclaimed.
Poul-Henning
In message <[EMAIL PROTECTED]>, Robert
Watson writes:
>
>Updated to a recent -CURRENT yesterday on on
Updated to a recent -CURRENT yesterday on one of my boxes, and noticed a
slightly unusual shutdown message:
syncing disks... 8 8 5 5 1 1
done
Reclaim 8 0 Killed
Uptime: 10h23m28s
Rebooting...
Don't know what it means, or if it's harmful, but it's certainly different
:-).
Robert N M
On Thu, 1 Feb 2001, Cejka Rudolf wrote:
> Sheldon Hearn wrote (2001/02/01):
> > What I remember of the discussions that surrounded this one, your
> > summary is correct. The only thing is that nice isn't so much _broken_
> > as it just isn't doing what you'd expect it to. :-)
>
> Ok, scheduler
On Sat, 03 Feb 2001 22:54:33 -0800 (PST), John Baldwin <[EMAIL PROTECTED]> said:
> The ppbus does painful things with its interrupt handlers. This
> is a known problem and on the todo list, just not fixed yet.
This problem (with lpr) is new in the past couple of days, at least
here ...
well, I got as far as importing ipfilter 3.4.16 into -current before I
realised that ref5 is not working properly (again) or for some reason
it just doesn't know about the ssh files that freefall does so if I
just broke -current, I'm sorry but if I could have done a test compile
on a 5.x box I wo
On Sun, Feb 04, 2001 at 02:03:22AM -0800, Doug Barton wrote:
> FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but
> there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X
> libraries in the directory, although I'm not sure what the right change
> would be.
Ar
FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but
there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X
libraries in the directory, although I'm not sure what the right change
would be.
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
Since mdconfig can autoallocate the device, why is this needed ?
In message <[EMAIL PROTECTED]>, Makoto MATSUSHITA writes:
>
>src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable
>(formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to
>configure md -- trivial, a
Greg Lehey wrote:
> On Friday, 2 February 2001 at 20:10:10 -0800, Peter Wemm wrote:
> > Robert Watson wrote:
> >
> >> crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci
> >
> > This one may appear harmless, but it is not. It is trivially easy to creat
e
> > an alignment fault (fatal
22 matches
Mail list logo
