Kernel panic (with uipc_domain.c, rev 1.33)

2003-09-02 Thread D. Rock
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

Re: ATAng probe updated please test

2003-09-02 Thread D. Rock
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

Re: ATA-ng

2003-08-31 Thread D. Rock
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

Re: Performance problems with 5.0-RELEASE

2003-01-28 Thread D. Rock
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

fsck cannot find superblock

2002-09-03 Thread D. Rock
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

CURRENT unstable during heavy file system I/O

2002-09-03 Thread D. Rock
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

Resource allocation error in new pnp code

2000-03-28 Thread D. Rock
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

ata: panic with new sysctl variable

2000-01-28 Thread D. Rock
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

Re: panic: isa_dmastart: bad bounce buffer

2000-01-04 Thread D. Rock
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 /kernel:

Re: ATA errors and AUTO_EOI

1999-12-21 Thread D. Rock
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 (for me at least)

problems with new pnp code

1999-12-15 Thread D. Rock
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

ATA problem

1999-12-15 Thread D. Rock
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,

Re: pcm driver breakage

1999-12-14 Thread D. Rock
irq 5 drq 1,0 on isa0 pcm0: SB DSP 3.01 on sbc0 pcm: setmap 3, ff00; 0xcd4b5000 - 3 pcm: setmap 4, ff00; 0xcd4c5000 - 4 Daniel "D. Rock" wrote: Hi, something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c The driver probes as a: pcm0: ESS1869 at

pcm driver breakage

1999-12-10 Thread D. Rock
Hi, something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c The driver probes as a: pcm0: ESS1869 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

pccard sio problems (Re: HEADSUP: wd driver will be retired!)

1999-12-09 Thread D. Rock
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 : taking

Re: ATA driver as the default

1999-12-08 Thread D. Rock
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 driver), the | system | crashed

Re: ATA driver as the default

1999-12-07 Thread D. Rock
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 laptop;

Re: rm error code on FAT

1999-11-09 Thread D. Rock
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 (i.e. EINVAL).

Re: ESS 1868 driver, again

1999-11-07 Thread D. Rock
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.

Re: sio working

1999-11-07 Thread D. Rock
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: device sio2at isa? po

Re: ESS 1868 driver, again

1999-11-06 Thread D. Rock
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 single tone. With the old voxware driver, so

Re: sio working

1999-11-06 Thread D. Rock
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 get is : sio2: configured irq -

Re: ESS 1868 driver, again

1999-11-06 Thread D. Rock
"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 "options PNPBIOS". You are running

Re: sio working

1999-11-06 Thread D. Rock
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 get is : sio2: configured irq -

Re: make world, attempt 5

1999-09-26 Thread D. Rock
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_INFO

Re: Loss of Functionality with newpnp

1999-09-26 Thread D. Rock
"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 (QD) solution for this problem:

Re: New PnP code does not work for me(?)

1999-09-26 Thread D. Rock
"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: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown1: Game at port 0x200-0x207 on isa0

Re: RealTek 8139 problems

1999-08-29 Thread D. Rock
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 hangs when it

dev_t and system accounting

1999-07-09 Thread D. Rock
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:

Re: dev_t and system accounting

1999-07-09 Thread D. Rock
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" and also

Re: config is broken?

1999-06-06 Thread D. Rock
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:

New ata driver gets intr statistics wrong

1999-03-04 Thread D. Rock
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

Re: ata1: unwanted interrupt

1999-03-03 Thread D. Rock
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 had no

Re: ata1: unwanted interrupt

1999-03-03 Thread D. Rock
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 block

Re: How to power off an ATX power supply machine on shutdown ?

1999-02-15 Thread D. Rock
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 were added

Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr

1999-02-11 Thread D. Rock
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

Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr

1999-02-11 Thread D. Rock
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:

Re: locale errors

1999-02-10 Thread D. Rock
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:

Re: locale errors

1999-02-05 Thread D. Rock
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_COLLATE to C, then

Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr

1999-02-05 Thread D. Rock
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 that

Re: locale errors

1999-02-04 Thread D. Rock
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 testing, i've

Re: locale errors

1999-02-04 Thread D. Rock
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 errors It is impossible. The collate couldn't detect

locale errors

1999-02-03 Thread D. Rock
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

No CD-ROM support in boot.flp?

1999-01-27 Thread D. Rock
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 ChangesPath

dirty fs after apm power off

1999-01-23 Thread D. Rock
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

Re: dirty fs after apm power off

1999-01-23 Thread D. Rock
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 filesystem is dirty and has to been

Re: NFS v3 issue

1999-01-22 Thread D. Rock
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 /usr/obj

NFS v3 issue

1999-01-21 Thread D. Rock
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

libexpcrypt?

1999-01-21 Thread D. Rock
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

Re: NFS problem found - pleaes try this patch.

1999-01-19 Thread D. Rock
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 because

Re: NFS woes: getting worse?

1999-01-15 Thread D. Rock
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

ESS 1868 driver, again

1999-01-03 Thread D. Rock
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