I've been having inexplicable crashes for a while and finally got around
to getting a debug kernel and checking out what's going on, so here
goes (apologies for the ^M's and all, I scripted a gdb session and that's
what I got...):
panic: bdwrite: buffer is not busy
panic messages:
---
Fatal t
W Gerald Hicks wrote:
> With the current hack^Wmethod used by make release we are
> required to add elements to a shell script which deletes items
> from the GENERIC configuration to create BOOTMFS.
>
> If my proposition holds water we can do away with the linkage
> to GENERIC in favor of a stati
Thomas Moestl <[EMAIL PROTECTED]> writes:
> (Disclaimer: my solution below is untested, so it may all be bogus)
As request, here are the test results.
Most rules work, except my final one:
%%%
bowie# ipfw add allow all from any to any
ipfw: getsockopt(IP_FW_ADD): Invalid argument
%%%
Here's a l
Ooh... yuh, i didn't read into detail of the log.
--
// Donny
W Gerald Hicks wrote:
> No, the problem is because the kernel has grown too large to
> fit on the md(4) filesystem prepared for it.
> src/release//dokern.sh needs to be adapted to omit
> new drivers added to GENERIC.
>> it look
I might propose that any driver supported under sysinstall needs to
support kldloading but I haven't really thought that through :-)
The issue here is that the BOOTMFS kernel has traditionally
(for freebsd) been derived by filtering GENERIC. GENERIC
has been changed in a way that causes BOOTMF
W Gerald Hicks wrote:
> No, the problem is because the kernel has grown too large to
> fit on the md(4) filesystem prepared for it.
>
> src/release//dokern.sh needs to be adapted to omit
> new drivers added to GENERIC.
All drivers not in the boot or install paths should be omitted, but
only if i
No, the problem is because the kernel has grown too large to
fit on the md(4) filesystem prepared for it.
src/release//dokern.sh needs to be adapted to omit
new drivers added to GENERIC.
Cheers,
Jerry Hicks
[EMAIL PROTECTED]
On Saturday, July 13, 2002, at 12:21 PM, Donny Lee wrote:
>
> Hi t
you can use addr2line to get info, but
at a pinch you can just use nm -n to figure out what function each address
is in.
On Sun, 14 Jul 2002, Szilveszter Adam wrote:
> Hello everybody,
>
> I have recently finished to upgrade my system to today morning's
> -CURRENT, with sources just *before* t
On Sun, Jul 14, 2002 at 11:08:07PM +0200, Marc Recht wrote:
> I'm getting strange dead-locks/complete lookups when I use the system
> ssh with port forwarding. Using something like:
> ssh -L8080:remote:8080 account@remote
> to forward a remote apache to my local box. When I access
> http://localh
Hi!
I'm getting strange dead-locks/complete lookups when I use the system
ssh with port forwarding. Using something like:
ssh -L8080:remote:8080 account@remote
to forward a remote apache to my local box. When I access
http://localhost:8080/ not later than the third click on link (or
pressing rel
On Sun, 2002/07/14 at 13:43:37 -0700, Luigi Rizzo wrote:
> [i am deliberately not trimming the email in case someone wants to
> look at the context]
>
> i am a bit dubious about your explaination -- it also does not
> explain why the person reporting this problem "fixed" that
> by swapping "times
[i am deliberately not trimming the email in case someone wants to
look at the context]
i am a bit dubious about your explaination -- it also does not
explain why the person reporting this problem "fixed" that
by swapping "timestamp" and "next_rule" in the structure
cheers
luigi
On Sun, 2002/07/14 at 01:18:10 -0700, Luigi Rizzo wrote:
> Hi,
> the following message seems to suggest that the compiler
> (the way it is invoked) packs structures differently
> when building the kernel and userland.
>
> The stize of the structure in question is computed
> by both kernel and use
On Sun, Jul 14, 2002 at 08:06:49PM +0200, Szilveszter Adam wrote:
> On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote:
> > Hello everybody,
> >
> > I have recently finished to upgrade my system to today morning's
> > -CURRENT, with sources just *before* the commit of rev 1.154 to
>
About a year ago I pushed for this to be integrated and
at that time there were lots of comments about
"not being done correctly and it will be done corectly soon".
well another year or so ha spassed and people are STILL
having to apply the patches manually.
Can I suggest that the code be applie
Hi,
> I'm still upset that we don't have tirpc99, when do you plan on porting
> that over?
I can do it now. I mostly stopped working on it, cause almost nobody
did care about to commit my patches bside you and Ian.
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
Thomas, what I find very interesting is that it still works regardless of
the commands that ATAPI don't understand, I know this is abit off topic,
but would any hardware expert mind explaining? :)
Will
On Sun, 14 Jul 2002, Thomas Quinot wrote:
> Le 2002-07-14, Willie Viljoen écrivait :
>
> > Ju
Le 2002-07-14, Willie Viljoen écrivait :
> Just to follow up, I went back to -STABLE after discovering I don't need
> -current to do this (*slight sigh of reliefe*)
Yep, I do most ATAPI/CAM develoment on -STABLE machines.
> Thomas, ever consider asking for it to be committed into FreeBSD proper
On Fri, Jul 12, 2002 at 07:50:00PM +0200, Michael Bretterklieber wrote:
> Hi,
>
> I installed FreeBSD 5.0-current on my notebook, because in FreeBSD4.6
> the sounddriver let the kernel hang on boot.
>
> I know, that acpi is under developement, but here are my results testing
> acpi on this har
Just to follow up, I went back to -STABLE after discovering I don't need
-current to do this (*slight sigh of reliefe*)
Thanks Jan and Thomas, it works perfectly with both my BTC 36x ATAPI
CD-ROM and the HP CD-Writer+ 9110.
Thomas, ever consider asking for it to be committed into FreeBSD proper,
>
> > Anybody have any idea what I need and where I can find it?
>
> http://www.cuivre.fr.eu.org/~thomas/atapicam/
Just as a datapoint, I recently applied the ATAPI/CAM patches to a -STABLE
from July 10th).
They applied flawlessly, compile was clean.
My newly-acquired TEAC DW-28E CDR/CDRW/DV
On Fri, Jul 12, 2002 at 05:29:01PM -0600, Eric Anholt wrote:
> > well if you give me details, i could try
>
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri -z3 co -P xc
>
ok i'll try :-) I am not a kernel hacker, so MMMV (my mileage my va
I'm still upset that we don't have tirpc99, when do you plan on porting
that over?
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductible donations for
On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote:
> Hello everybody,
>
> I have recently finished to upgrade my system to today morning's
> -CURRENT, with sources just *before* the commit of rev 1.154 to
> src/sys/kern/kern_fork.c by Julian.
>
> I have an UP IA32 machine, I am no
Hello everybody,
I have recently finished to upgrade my system to today morning's
-CURRENT, with sources just *before* the commit of rev 1.154 to
src/sys/kern/kern_fork.c by Julian.
I have an UP IA32 machine, I am not using any additional kernel modules,
and now, upon rebooting with the new kern
Hi all,
I reworked my patch as from PR bin/29175 and the PR
misc/27816.
http://people.freebsd.org/~mbr/patches/rpcgen.diff
Some comments about the patch.
- TI-RPC is now the default again for code generation. Unbreaks
ports/mail/drac for CURRENT.
- As before, inetd support support is turne
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Just a note for those following these things...
Not of great importance, as we know that -current
performance will go up and down,
but I just noticed we lost 1.5% since the 9th
on the "worldstone" test. (real time numbers. several runs)
July 14 kernel
3441.946u 1492.986s 1:32:01.33 89.3%2726+
> Anybody have any idea what I need and where I can find it?
http://www.cuivre.fr.eu.org/~thomas/atapicam/
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi, I was scratching around the geocrawler archives yesterday, looking for
information on using SCSI emulation in FBSD. I found some, but was dumb
enough (yet again) not to bookmark it.
I've synced my source with -CURRENT, and looked through all the options I
could find, even a home-made LINT, st
Luigi Rizzo wrote:
> Hi,
> the following message seems to suggest that the compiler
> (the way it is invoked) packs structures differently
> when building the kernel and userland.
>
> The stize of the structure in question is computed
> by both kernel and userland app using sizeof(),
> so there i
Hi,
the following message seems to suggest that the compiler
(the way it is invoked) packs structures differently
when building the kernel and userland.
The stize of the structure in question is computed
by both kernel and userland app using sizeof(),
so there is no assumption on the size of its
32 matches
Mail list logo
