Hi,
the new dev_t stuff in the kernel keeps system accounting showing up
the tty properly. After taking a look at the fix for the swap device,
I propose the following equivalent fix:
Index: kern/kern_acct.c
===
RCS file: /data/cvs/s
> >Hi,
> >
> >the new dev_t stuff in the kernel keeps system accounting showing up
> >the tty properly. After taking a look at the fix for the swap device,
> >I propose the following equivalent fix:
>
> Looks good, could you try this version for me ?
[patch deleted]
I recompiled a "make world" an
Josh Tiefenbach schrieb:
>
> > :NFS append race @0:19
>
> [snip]
>
> > There were a bunch of situations that could cause this, including an
> > append race for which the debug message was named after. The append
> > race is now fixed but there are still a few situations that can
Nick Hibma wrote:
>
> Starting mpg123 with a random mpg3 file produces the following panic
> within half a second. The kernel is current as of this morning. THe
> panic is reproducable (as in, I cannot play the mpg3 file).
>
> kernel plus core available if needed.
>
> Dec 15 14:55:25 henny /ker
Hi,
just noticed the new sysctl variable for ata. I just wanted to
use the new way for disabling DMA on my disk (has some strange
problems, even under windows).
Previously I just commented out the ata_dmainit() lines in
ata_disk.c, now I wanted to set it with sysctl:
sysctl -w hw.atamodes="pio,
Hi,
I get some strange networking results with my RealTek 8139 card. I
don't know how long these problems exist in the kernel, because they
only showed up after some change in my network setup.
I got a third PC for testing and now needed a hub to connect all my
PCs together. I used to have an UT
Bruce Evans schrieb:
>
> >Under normal Circumstances, the communication is Ok between all three
> >machines, but sometimes the ethernet interface in the main machine
> >(the 8139) wedges up. I cannot ping any other host. The only solution
> >is taking the interface down and up again:
>
> It hang
Greg Lehey schrieb:
>
> I've been trying for the last 24 hours solid to make a new world. The
> latest problem is:
>
> ===> libwrap
> cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP
>-DDAEMON_UMASK=022 -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS
>-DSEVERITY=LOG_
"Donald J . Maddox" schrieb:
> Is the new PnP code really so smart that it has no use for user intervention
> ever? My experience indicates that it is not.
>
> It would be very nice if the architects of the new PnP code would add back
> this lost functionality.
My (Q&D) solution for this problem
"Donald J . Maddox" schrieb:
>
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead. All I get is:
>
> unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: at port 0x200-0x207 on isa0
> unkno
I read the last mails regarding problems with their ESS 1868 boards.
Well, at least it is partially working for them. I didn't have any
luck with the driver for some time now. I couldn't get a single tone.
With the old voxware driver, sound worked at least partially
(44.1 kHz, 8 Bit, mono), but w
Warner Losh wrote:
>
> OK. I managed to get sio and ep working on the plane back from
> FreeBSDCon'99. There are some problems with card eject at the moment,
> but will be committing things to the tree shortly.
>
> Basically, I completely gutted the compatibilty layer and it became
> much easi
Peter Wemm wrote:
>
> "D. Rock" wrote:
> > I read the last mails regarding problems with their ESS 1868 boards.
> > Well, at least it is partially working for them. I didn't have any
> > luck with the driver for some time now. I couldn't get a sing
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> "D. Rock" writes:
> : I tried many different combinations. I disabled the onboard serial devices
> : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
> : irq 4 but the only thing I
"D. Rock" wrote:
> > > Here my configuration:
> > > device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15
> >
> > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and
> > nothing more. You might also try
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> "D. Rock" writes:
> : I tried many different combinations. I disabled the onboard serial devices
> : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with
> : irq 4 but the only thing I
Peter Wemm wrote:
> As to why the 1869 isn't working for you, that's anybody's guess. You
> might try posting the 'dmesg' output (not from syslog) and your complete
> config file, as well as any other pertinant information you can think of.
Ok
here is the (hopefully) complete information.
-curr
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> "D. Rock" writes:
> : device sio0at isa? port IO_COM1 flags 0x10 irq 4
> : device sio1at isa? port IO_COM2 irq 3
>
> These look good. IIRC, the kernel I tested with also had:
&
Hellmuth Michaelis wrote:
>
> >From the keyboard of Charlie ROOT:
>
> > During make of kernel:
> >
> > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../
Maxim Sobolev wrote:
>
> "Matthew D. Fuller" wrote:
>
> > On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me
> > that Maxim Sobolev remarked
> > >
> > > If your logic is right, then attempt to remove existent files from FAT using
> > > '*' should yield absolutely the same result (
"Daniel C. Sobral" wrote:
>
> "D. Rock" wrote:
> >
> > options HZ=500
>
> Without this line, do things work?
No, but I finally got an at least partial solution:
I had to configure to use DMA channels 1,0 (it used to be 1,5).
Even 0,1 did
David O'Brien schrieb:
>
> Since the ATA driver is destined to be the default in 4.0-R, and we hare
> hitting the feature freeze date; can we make the switch now?
>
> I think it is very important to get ATA into more hands to see where it
> breaks. It certainly has problems on my Vaio 505 lapto
Doug Ambrisko schrieb:
>
> D. Rock writes:
> | I just re-enabled the ATA driver again after reading the change log
> | of better error handling and automatic falldown DMA->PIO under specific
> | circumstances.
> | But a few days later, while making world (with the ata dr
Zitiere Daniel Eischen <[EMAIL PROTECTED]>:
> > In message <[EMAIL PROTECTED]>
Christopher Masto
> writes:
> > : Right now, I have no sound (not detected), no USB
(panic on removal),
> > : can\\\'t use my sio pccard, can\\\'t
eject my ed
pccard, my IDE drives are
> > :
Hi,
something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c
The driver probes as a:
pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
The relevant kernel config entries are
device pcm0
options PNPBIOS
With the new revision, while playing pcm audio, I can
0x331 irq 5 drq 1,0 on
isa0
pcm0: on sbc0
pcm: setmap 3, ff00; 0xcd4b5000 -> 3
pcm: setmap 4, ff00; 0xcd4c5000 -> 40000
Daniel
"D. Rock" wrote:
>
> Hi,
>
> something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c
>
> The driver prob
Hi,
just noticed a bug in the new pnp code. The resource allocator
seems to ignore the align flag for port addresses.
dmesg output:
[...]
AZT5001: start dependant
AZT5001: adding io range 0x100-0x3ff, size=0x1, align=0x1
AZT5001: end dependant
[...]
SAG0001: start dependant
SAG0001: adding io ra
Hi,
The ata driver tries to enable UDMA for my controller, but fails
(this is no disk problem. The disks can do UDMA, as tested in
another machine). Perhaps UDMA should be disabled for all
VIA 82C586 chips:
dmesg output:
[...]
found-> vendor=0x1106, dev=0x0571, revid=0x02
class=01-01-8a,
Hi,
yesterday I reported a bug in the resource allocator
for PnP ISA devices:
The align-field is ignored for IO port resources, e.g.
device A wants io range 0x100-0x3ff, size=0x1, align=0x1
device B wants io range 0x100-0x3f7, size=0x8, align=0x8
device A gets assigned first and will receive
a
Oliver Fromme schrieb:
>
> Doug White wrote in list.freebsd-current:
> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > > It seems Dieter Rothacker wrote:
> > > > The solution for me was to recompile the kernel without AUTO_EOI1 and
> > > > AUTO_EOI2.
> > >
> > > Those options newer worked (
Hi,
I already mentioned this bug a few months ago but didn't got a reply. Maybe
I'm the only one who is affected by this bug.
I have several PnP cards in my system (see attached output of pnpinfo).
Especially one card requests a resource:
I/O Range 0x100 .. 0x3ff, alignment 0x1, len 0x1
> From [EMAIL PROTECTED] Tue Jul 31 12:15:25 2001
>
> set debug.acpi.timer_test="yes"
>
> at the loader prompt and boot? Ideally, you'll get a message "timer is
> not monotonic", followed by some numbers. If this is the case, then I
> need to get "smarter" with the ACPI timer probe.
acpi0:
I have similar experiences. I sometimes do a "make release" with an NFS
mounted chroot environment. My latest successful build is dated from
Dec 21. All of the later builds (starting Jan 6th) failed. The error
seems to be very deterministic though. I have at least a lot of garbage
in /usr/include,
This patch seems to fix my NFS problems. I started a make release yesterday
and it is still running (It's a slow machine). No problems so far.
The chroot dir is NFSv2/UDP mounted.
Thanks,
Daniel
Luoqi Chen schrieb:
>
> The check is correct and should be there, the B_CACHE bit was cleared becaus
With NFS v3 there seem still to be some open issues.
Im running the latest (4.0)-current with the new vm/NFS changes.
While I haven't found any problems with NFSv2 so far, v3 still seems to make
trouble.
I noticed the error some months ago, while my /usr/obj was NFS mounted, and
a build failed whi
Hi,
after todays build I wasn't able to login:
Instead of installing libdescrypt.* and linking libcrypt.* to libdescrypt.*
I suddenly got libexpcrypt.* files, with no DES code in.
It seems the international secure distribution isn't in sync any more.
I am missing /usr/src/secure/lib/libcrypt/crypt
Matthew Dillon schrieb:
>
> :With NFS v3 there seem still to be some open issues.
> :Im running the latest (4.0)-current with the new vm/NFS changes.
> :While I haven't found any problems with NFSv2 so far, v3 still seems to make
> :trouble.
> :
> :I noticed the error some months ago, while my /us
I have noticed this behaviour on at least one machine.
If I shutdown the machine with apm power off, the filesystem is dirty and
has to been checked on the next reboot. It seems, the power is cut too fast.
I don't have any problems with reboots.
It seems the drive doesn't have the time to write the
uffle the carefully sorted file system blocks.
Daniel
> probably the drive needs write-caching turned off...
>
>
> On Sat, 23 Jan 1999, D. Rock wrote:
>
> > I have noticed this behaviour on at least one machine.
> > If I shutdown the machine with apm power off, the fi
>jkh 1999/01/26 07:14:11 PST
>
> Modified files:
>release/scripts doFS.sh dokern.sh
> Log:
> 1. Adjust fs sizes to get floppies back under control.
>
> 2. Viciously slash all CD support out of boot.flp. It's basically just
> a net boot floppy now.
>
> Revision Chang
While browsing through some directories I noticed an annoying error
in locale based sorting.
My LANG is set to de_DE.ISO_8859-1
Sorting treats "ss" as a single character instead of two. This leads
to some interesting (at least) errors in displaying sorted output.
My locale is set do de_DE.ISO_88
J Wunsch schrieb:
>
> As Andrey A. Chernov wrote:
>
> > > I suggest removing any multi character definition out of the collate
> > > files.
> >
> > It was Joerg initiative, I don't know DE enough to judge here. Please
> > resolve this problem with him (CC'ed).
>
> Well, not completely. :) For
Ladavac Marino schrieb:
>
> > -Original Message-
> > From: D. Rock [SMTP:r...@cs.uni-sb.de]
> > Sent: Thursday, February 04, 1999 10:36 AM
> > To: Joerg Wunsch
> > Cc: Andrey A. Chernov; curr...@freebsd.org
> > Subject: Re: locale e
> > My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII
> > If I type 2 characters ss, I mean 2 characters ss. If I type ß I
> > mean the single character ß.
> > This sorting behaviour is just wrong. Not every apperence of "ss"
> > even in pure ASCII does mean "ß".
>
> I suggest you set LC_COLL
Matt wrote:
> This is very odd. This is the approximate backtrace that I get
> when I throw my test machine into DDB:
[..]
> What is happening is that I am doing a 'make installworld' on my
> test machine with / and /usr NFS V3 mounted R+W.
I also have come to the conclusion tha
I think I have found a solution. The problem with the current definition is,
that "ss" is folded into one character, while "ß" should be expanded to "ss"
and sorted accordingly.
I read the manual pages of colldef and found a solution, which sorted my
test patterns right.
ndex: data/de_DE.ISO_8859
This doesn't fix my problem (my isn't even rename or delete related)
As I writed some time before, I always get the wrong results if I generate
the termcap.db in an NFSv3 mounted directory. It doesn't matter which machine
is the NFS server (tried Solaris 7 and the NFS client machine itself). The
g
> >As I writed some time before, I always get the wrong results if I generate
> >the termcap.db in an NFSv3 mounted directory. It doesn't matter which machine
> >is the NFS server (tried Solaris 7 and the NFS client machine itself). The
> >generated file has *always* the wrong size (always the same
> > > Is a delay needed between the final sync's and the actual power off?
> >
> > Apparently so. There is/was a recently added sysctl for this purpose.
> > Poke around in the archives.
> >
>
> Was that sysctl added to the -STABLE branch? I am running 3.1-BETA
> and I cannot find it.
No, they w
> >After having CVSupped to the latest 4.0-CURRENT tree
> > (just now), I noticed the amazing speed of the new ATA driver.
>
> The amazing speed of the new ATA driver? Were you using 32 bit transfers
> and multi-sector IO with the older driver?
>
> I assumed from the benchmarks posted that I
> > Am I confused (yet again)?
>
>Yes ;-)
>
>I mean the time it takes to actually detect the drive.
I recently added
options IDE_DELAY=2000
on all IDE kernels I managed. The only problem with this short delay
so far was an undetected drive in an unusual configuration:
The jumper b
Interrupts don't get accounted right. Instead of adding them to irq14/irq15
they always seem to be added to irq0.
Here is a sample output of systat (I have "options HZ=1000" in my kernel
config, so 1000 should be normal)
3 usersLoad 1.21 1.05 1.01 Do 4 Mär 02:04
Mem:
Dan Nelson schrieb:
In the last episode (Jan 23), Rahul Siddharthan said:
Kenneth Culver wrote:
Did you by any chance build your own kernel? If so did you leave
things like this in:
options INVARIANTS #Enable calls of extra sanity
options INVARIANT_SUPPORT #
Soren Schmidt schrieb:
It seems Chris Petrik wrote:
Think it would be a wise thing to do is to make a kernel option to use ATAng
and one to use the old ATAold or something you commited a important part of
the system without throughly testing it and most people dont use SMP i would
think to do i
Hi,
latest kernel causes a panic early during boot:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc02667cf
stack pointer = 0x10:0xc0641cf8
frame pointer
Soren Schmidt schrieb:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hi,
again no luck. Same problem persists, the devices got probed correct
This option is in /sys/conf/options and /sys/i386/conf/options.i386
According to the cvs log, the floppy driver has moved out of the i386
architecture directory. It seems the options.i386 has been forgotten
(options.pc98 has been corrected).
Daniel
Alex Zepeda schrieb:
>
> redwood201:/usr/src/s
Hi,
I get a reproduceable panic each time I run the command "sysctl -a"
Stack backtrace from a panic'd kernel:
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc025f6e9 in boot (howto=256) at ../../../kern/kern_shutdown.c:372
#2 0xc025f9e9 in panic () at ../../../kern/kern_sh
Poul-Henning Kamp schrieb:
Can you try this patch ?
[patch deleted]
Thanks for the fast response.
Patch works for me - no more panic.
--
Daniel
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscrib
Hi,
with 'uncommon' block sizes fsck seems to have problems finding the
superblock:
# newfs -i 10240 -b 4096 -f 512 /dev/ad1d
Reduced frags per cylinder group from 26208 to 26200 to enlarge last cyl group
/dev/ad1d: 409.6MB (838860 sectors) block size 4096, fragment size 512
using 33 cy
Hi,
since some months now my -CURRENT is very unstable during heavy file system
activity (parallel accesses while deleting large subdirectories).
Today, I ran the following command for simple cleanup of /usr/ports:
# find /usr/ports -type d -name work -print | xargs rm -rf
[Yes, I should have
61 matches
Mail list logo
