Re: Is booting/installing from USB CDROM considered supported?
Martin Nilsson wrote: I tried to install our CD/FDD-less servers from a CD-RW drive connected on the USB port, I'll try with a fresh 5.2-BETA later today and see what happens with it. in the meantime I just want to ask: The 5.2-BETA CDROM hangs, it prints something like found /BOOT/LOADER ... and then nothing else happens. Does anyone know what might be the problem and where one should look to try to fix it? The motherboard is a Supermicro P4SGE with an external 52x Asus CD-RW unit. I have tried with and without USB FDD, no differnce. WinXP installs as as usual (but very slowly) on this combination. -- Martin Nilsson, CTO Founder, Mullet Scandinavia AB, Malmö, SWEDEN E-mail: [EMAIL PROTECTED], Phone: +46-(0)708-606170, Web: www.mullet.se Our business is well engineered servers optimised for FreeBSD Linux ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on i386/i386
TB --- /home/des/tinderbox/CURRENT/i386/i386/lock: flock(): Resource temporarily unavailable TB --- ERROR: unable to lock sandbox ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thinkpad T40p and panic during boot...;O
Just in case anyone didnt know already ;) Jeffrey Katcher wrote: You have to set: hw.pci.allow_unsupported_io_range=1 at startup initially and then in /boot/loader.conf for subsequent boots I had the same problem, now I'm happily running 5.1-Current/5.2-Beta. Finnur Guðmundsson wrote: Hi there! ;) I´ve been trying to install FreeBSD-CURRENT and FreeBSD 5.2-BETA on my Thinkpad for awile The problem is this: When i try to boot 5.1-Current (first cd i tried was from 5 Oct 2003 and the latest one was 5.2-BETA) i get this error: ---CUT--- Memory modified after free 0x20e1800(2044) val=c4c24510 @ 0xc20e1ac4 panic: Most recently used by bus Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 ---CUT--- I have the newest bios for this puter, and have tried without acpi, safe mode, and defaultnothing seems to boot this baby! ;) It boots 5.1-Release, but then i cant use the network card, it says something about bad eprom (its intel 10/100/1000 cardem0 WellIf anyone gets idea or if you guys need more info, just ask ..didnt thing of anything you guys wanted more. - Finnzi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: psmintr not attached w/ acpi
Has anyone looked into pr i386/54781? It sounds very similar, and it doesn't happen only on intel laptops. It also happens on my athlon laptop. -- Russell A. Jackson ([EMAIL PROTECTED]) The irony is, if you're willing to kill a perpetrator, you probably won't have to. -- Massad Ayoob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAPI CD still not detected, verbose boot logs available
Could you try this simple patch and see if that helps?
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.23
diff -u -r1.23 ata-lowlevel.c
--- ata-lowlevel.c 2 Nov 2003 22:04:53 - 1.23
+++ ata-lowlevel.c 3 Dec 2003 07:50:44 -
@@ -575,7 +575,7 @@
}
}
}
- if (stat1 ATA_S_BUSY) {
+ if (!((mask == 0x03) (stat0 ATA_S_BUSY)) (stat1 ATA_S_BUSY)) {
ATA_IDX_OUTB(ch, ATA_DRIVE, ATA_D_IBM | ATA_SLAVE);
DELAY(10);
-Søren
.. but it works under windows!!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [ATAng?] ad1 disappeared again
It seems Chris Faulhaber wrote:
I have been seeing the same issue since August with a different,
but similiar, set of drives:
ad0: 57241MB ST360015A [116301/16/63] at ata0-master UDMA100
ad1: 57241MB ST360015A [116301/16/63] at ata0-slave UDMA100
Under -CURRENT only the first drive is seen; RELENG_4 still works
fine.
Could you try this patch and get back to me with the result please:
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.23
diff -u -r1.23 ata-lowlevel.c
--- ata-lowlevel.c 2 Nov 2003 22:04:53 - 1.23
+++ ata-lowlevel.c 3 Dec 2003 07:50:44 -
@@ -575,7 +575,7 @@
}
}
}
- if (stat1 ATA_S_BUSY) {
+ if (!((mask == 0x03) (stat0 ATA_S_BUSY)) (stat1 ATA_S_BUSY)) {
ATA_IDX_OUTB(ch, ATA_DRIVE, ATA_D_IBM | ATA_SLAVE);
DELAY(10);
-Søren
.. but it works under windows!!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test pcm channel patch
Hello All, Please test this PCM patch. It creates seperate locking classes for PCM channels and should prevent the warning where multiple mutexes from the same class are held (as reported recently). I believe this to be a good strategy as it masks fewer errors. I can confirm that this patch fixes my LOR for pcm(4). -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test pcm channel patch
Hello All, Please test this PCM patch. It creates seperate locking classes for PCM channels and should prevent the warning where multiple mutexes from the same class are held (as reported recently). I believe this to be a good strategy as it masks fewer errors. I can confirm that this patch fixes my LOR for pcm(4). -sc Bah! I got 30min into playing tunes and picked the same LOR up not more than 5min after sending this. :( Sorry for the false alarm. acquiring duplicate lock of same type: pcm record channel 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144 2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146 Stack backtrace: -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
jail and emulators/linux_base
Hi all, I'm running CURRENT and set up a jail where I want to install SUN JDK 1.4.2. In the process, linux emulation needs to be installed. While installing emulators/linux_base, I get the following: === Installing for linux_base-7.1_5 Un-mounting linprocfs... umount: retrying using path instead of file system ID === Generating temporary packing list === Checking if emulators/linux_base already installed mknod: /compat/linux/dev/null: Operation not permitted *** Error code 1 While Linux-emulation is already up and running on the host-machine, it seems the jail is not allowed to create what it needs to run it. I understand allowing mknod(8) within a jail is dangerous in the case where you allow untrusted users to be root. Is there some way to either say I don't let untrusted users be root thus allowing this or to compile emulators/linux_base more jail-friendly, possibly setting things up from outside the jail? About compiles, btw, they seem to drag out forever in a jail. Especially configure takes ridiculous long time. I was under the impression that the overhead of running a jail should be very small, yet compiling shells/bash2 in a fresh jail took 8 minutes and 8.6 seconds while compiling it on the host system took 54.9 seconds. Are there options that may affect jail-performance I can tune? Cheers Niklas Saers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: problem with kerberos startup and LDAP
Hello All, I have the same problem. See also PR58680. http://www.freebsd.org/cgi/query-pr.cgi?pr=58680 Guys who work on RCNG please consider the proposed solution. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean McNeil Sent: Monday, December 01, 2003 9:37 AM To: [EMAIL PROTECTED] Subject: problem with kerberos startup and LDAP Hello All, I was having trouble with startup and kdc/kadmin5 failing. Turns out that they were trying to access a shared library in /usr/local/lib (libldap.so.2). Unfortunately, both were getting started before ldconfig. I added ldconfig to the REQUIRE: for kerberos and now all is well. What should be the correct solution? Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: licq KSE - resolved
Daniel Eischen wrote: If I use libkse I get: kernel: Warning: pid 25341 used static ldt allocation. kernel: See the i386_set_ldt man page for more info in my messages. When I use libc_r I do not get this messages. I'm sorry. Messages seems to be independent from library. I get messages with both libraries but not every time. Some times I get two messages on one licq launching. But with libc_r it works and with libkse is not. It is not libkse that is causing the messages. It is some library or driver that licq is using. The kernel spews these messages whenever something uses static LDT allocation. We know that nvidia drivers and/or their OpenGL library do this, and they have been notified of it (by me). If there is another library or application that is also using static LDT allocation, please help us find it so it can be fixed also. $ ldd /usr/local/bin/licq From which system is this? The nvidia or the ATI? We know nvidia I try to use same HDD on two systems. On system with ATI video I only disable nvidia kernel module loading and change X driver. has a problem with ldt/%gs usage. You still haven't told me if you are getting the same static LDT warnings from the ATI system. Yes. I get this warning on both systems with both libraries but only fist 10 times after system reboot. /usr/local/bin/licq: libssl.so.3 = /usr/lib/libssl.so.3 (0x28102000) libcrypto.so.3 = /lib/libcrypto.so.3 (0x28134000) libc_r.so.5 = /usr/lib/libc_r.so.5 (0x28242000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x28266000) libm.so.2 = /lib/libm.so.2 (0x28322000) libc.so.5 = /lib/libc.so.5 (0x2833b000) $ ldd ./licq_qt-gui.so ./licq_qt-gui.so: libqt-mt.so.3 = /usr/X11R6/lib/libqt-mt.so.3 (0x2828e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x288d) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x288d9000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x288f) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x289b8000) libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x289c7000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x289e5000) libm.so.2 = /lib/libm.so.2 (0x28aa1000) libmng.so.1 = /usr/local/lib/libmng.so.1 (0x28aba000) libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28b18000) libz.so.2 = /lib/libz.so.2 (0x28b3d000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x28b4b000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28bb2000) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x28bc8000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x28bd) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28be2000) libfontconfig.so.1 = /usr/X11R6/lib/libfontconfig.so.1 (0x28c4c000) liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28c74000) libGLcore.so.1 = /usr/X11R6/lib/libGLcore.so.1 (0x28c8f000) ^^ What is this? Oh!!! This is library from nvidia driver. Nvidia driver replaces libGL.so and new libGL require libGLcore.so. After full deleting of nvidia driver port from system proglem is gone. Now licq works fine with libkse. Thanks! PS: How about new version of nvidia driver? How can I use nvidia driver and libkse on same machine? libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x2912b000) libexpat.so.4 = /usr/local/lib/libexpat.so.4 (0x2917c000) This doesn't match mine: /usr/local/lib/licq/licq_qt-gui.so: . libqt-mt.so.3 = /usr/X11R6/lib/libqt-mt.so.3 (0x2828e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x2894c000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x28955000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x2896c000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x28a34000) libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x28a43000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x28a61000) libm.so.2 = /lib/libm.so.2 (0x28b1d000) libc_r.so.5 = /usr/lib/libkse.so.1 (0x28b36000) libmng.so.1 = /usr/local/lib/libmng.so.1 (0x28b5b000) libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28bb9000) libz.so.2 = /lib/libz.so.2 (0x28bde000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x28bec000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28c59000) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x28c6f000) libXrandr.so.2 = /usr/X11R6/lib/libXrandr.so.2 (0x28c77000) libXcursor.so.1 = /usr/X11R6/lib/libXcursor.so.1 (0x28c7b000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x28c84000) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28c96000) libfontconfig.so.1 =
FreeBSD 5.x and Bad File Descriptor errors. Why?
Hello What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am considering going back to it but I need to figure out how to prevent this issue from happening again. My system has 2 harddrives, a 16 GB Seagate that I use for backups and mount it under /mnt/backup and a 40 GB Maxtor that I am using for everything else. After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. Now if not for a few things, I'd probably come to the conclusion that my Maxtor HD is dying on me as my Seagate drive isn't causing me any headaches. However this doesn't seem to be the case, as if Linux (EXT3) or Windows (NTFS) are used, no data loss ever occurs even if the system is left running for many weeks in a row. Now what exactly could be causing this bizarre behavior ? If this is of any help, the exact model number of the HD is MAXTOR 4K040H2 and I was using UFS2 on both drives. Thanks in advance. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jail and emulators/linux_base
On Wed, Dec 03, 2003 at 10:22:16AM +0100, Niklas Saers Mailinglistaccount wrote: + I'm running CURRENT and set up a jail where I want to install SUN JDK + 1.4.2. In the process, linux emulation needs to be installed. While + installing emulators/linux_base, I get the following: + + === Installing for linux_base-7.1_5 + Un-mounting linprocfs... + umount: retrying using path instead of file system ID + === Generating temporary packing list + === Checking if emulators/linux_base already installed + mknod: /compat/linux/dev/null: Operation not permitted + *** Error code 1 + + While Linux-emulation is already up and running on the host-machine, it + seems the jail is not allowed to create what it needs to run it. I + understand allowing mknod(8) within a jail is dangerous in the case where + you allow untrusted users to be root. Is there some way to either say I + don't let untrusted users be root thus allowing this or to compile + emulators/linux_base more jail-friendly, possibly setting things up from + outside the jail? Erm. You may install it using chroot(8) only and then run jail with the same path. You may also use chroot(8) instead of jail if you're looking for full functionality. -- Pawel Jakub Dawidek [EMAIL PROTECTED] UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net pgp0.pgp Description: PGP signature
Re: PANIC: PAGE FAULT
On Wed, 3 Dec 2003, Ganbaa wrote: I'm trying to install FreeBSD-5.1 on the PC with PIII,512MB SDRAM, 30GB Barracuda II Model ST330630A. But following error has occured. We're in the throes of preparing FreeBSD 5.2 for release, which includes a large number of bug fixes (although potentially a fair number of bugs, as we're still in the beta). I think it might make sense to try grabbing the 5.2-ISO from the FTP site and see if you can install that. If you run into the same bug, it includes a kernel.debug and debugging information we can use to debug the problem. If you run into a different bug, we can work to fix that, or better yet, it might just work :-). Regardless of whether you stick with 5.2 during the test cycle, the results would be very helpful to make sure 5.2 will work on your hardware even if 5.1 doesn't. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code= supervisor read, page not present instruction pointer = 0x8:0xc035eb26 stack pointer = 0x10:0xdba72bb8 frame pointer = 0x10:0xdba72c2c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 80 (sh) trap number = 12 panic: page fault syncing disks, buffers remaining... 184 184 184 184 184 184 184 184 184 184 184 184 184 184 giving up on 148 buffers Uptime: 16s Terminate ACPI PLEASE HELP ME!!! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: initiate_write_inodeblock_ufs2: already started
Ran into this on a box with -CURRENT from yesterday, running with MAC
(although in this case I suspect it doesn't make a difference, I'm not
using the multilabel/extattr code in UFS2). I have a core on disk, so
please let me know what further information would be useful. This machine
spends a lot of time in bgfsck these days due to a bug causing X Windows
to occasionally hang when starting (interestingly, it seems to start much
better when bgfsck is running, suggesting a race that's avoided by slowing
the system down...)
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Senior Research Scientist, McAfee Research
Script started on Wed Dec 3 08:04:46 2003
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-undermydesk-freebsd...
panic: initiate_write_inodeblock_ufs2: already started
panic messages:
---
panic: initiate_write_inodeblock_ufs2: already started
cpuid = 0;
syncing disks, buffers remaining... 3834 3834 3829 3829 3829 3829 3829 3829 3829 3829
3829 3829 3829 3829 3829 3829 3829 3829 3829 3829 3829 3829
giving up on 2705 buffers
Uptime: 9h20m19s
Dumping 511 MB
[CTRL-C to abort] 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288
304 320 336 352 368 384 400 416 432 448 464 480 496
---
Reading symbols from /boot/kernel/snd_maestro3.ko...done.
Loaded symbols for /boot/kernel/snd_maestro3.ko
Reading symbols from /boot/kernel/snd_pcm.ko...done.
Loaded symbols for /boot/kernel/snd_pcm.ko
Reading symbols from
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_biba/mac_biba.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_biba/mac_biba.ko.debug
Reading symbols from
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_mls/mac_mls.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/mac_mls/mac_mls.ko.debug
Reading symbols from /boot/kernel/r128.ko...done.
Loaded symbols for /boot/kernel/r128.ko
Reading symbols from
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linprocfs/linprocfs.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linprocfs/linprocfs.ko.debug
Reading symbols from
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linux/linux.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/PAPRIKAMAC/modules/usr/src/sys/modules/linux/linux.ko.debug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc0671987 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc0671d8d in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc07cf179 in initiate_write_inodeblock_ufs2 (inodedep=0xc58c2880, bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3902
#4 0xc07ce30d in softdep_disk_io_initiation (bp=0xcec33148)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3468
#5 0xc0635547 in spec_xstrategy (vp=0xc49c4514, bp=0xcec33148)
at /usr/src/sys/sys/buf.h:413
#6 0xc06356e2 in spec_specstrategy (ap=0xd7830bf0)
at /usr/src/sys/fs/specfs/spec_vnops.c:534
#7 0xc0634828 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:122
#8 0xc06b8324 in bwrite (bp=0xd7830bf0) at vnode_if.h:1141
#9 0xc06ba152 in vfs_bio_awrite (bp=0xcec33148)
at /usr/src/sys/kern/vfs_bio.c:1715
#10 0xc06c2307 in vop_stdfsync (ap=0xd7830cd4)
at /usr/src/sys/kern/vfs_default.c:738
#11 0xc06353e0 in spec_fsync (ap=0xd7830cd4)
at /usr/src/sys/fs/specfs/spec_vnops.c:422
#12 0xc0634828 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:122
#13 0xc06ca516 in sched_sync () at vnode_if.h:627
#14 0xc065b2f4 in fork_exit (callout=0xc06ca290 sched_sync, arg=0x0,
---Type return to continue, or q return to quit---
frame=0x0) at /usr/src/sys/kern/kern_fork.c:793
(kgdb) up
#1 0xc0671987 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
372 doadump();
(kgdb) up
#2 0xc0671d8d in panic () at /usr/src/sys/kern/kern_shutdown.c:550
550 boot(bootopt);
(kgdb) up
#3 0xc07cf179 in initiate_write_inodeblock_ufs2 (inodedep=0xc58c2880, bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3902
3902panic(softdep_write_inodeblock: lost dep3);
(kgdb) list
3897for (i = 0; i NIADDR; i++) {
3898#ifdef DIAGNOSTIC
3899if (dp-di_ib[i] != 0
3900(deplist ((1 NDADDR) i)) == 0) {
3901FREE_LOCK(lk);
3902
Re: licq KSE - resolved
On Wed, 3 Dec 2003, Alexander Motin wrote: Daniel Eischen wrote: From which system is this? The nvidia or the ATI? We know nvidia I try to use same HDD on two systems. On system with ATI video I only disable nvidia kernel module loading and change X driver. Right, it's not only the module but the OpenGL library -- see your response below. has a problem with ldt/%gs usage. You still haven't told me if you are getting the same static LDT warnings from the ATI system. Yes. I get this warning on both systems with both libraries but only fist 10 times after system reboot. The kernel only prints out the warning for the first 10 times it detects the static ldt usage. ./licq_qt-gui.so: libqt-mt.so.3 = /usr/X11R6/lib/libqt-mt.so.3 (0x2828e000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x288d) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x288d9000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x288f) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x289b8000) libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x289c7000) libstdc++.so.4 = /usr/lib/libstdc++.so.4 (0x289e5000) libm.so.2 = /lib/libm.so.2 (0x28aa1000) libmng.so.1 = /usr/local/lib/libmng.so.1 (0x28aba000) libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28b18000) libz.so.2 = /lib/libz.so.2 (0x28b3d000) libGL.so.1 = /usr/X11R6/lib/libGL.so.1 (0x28b4b000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28bb2000) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x28bc8000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x28bd) libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x28be2000) libfontconfig.so.1 = /usr/X11R6/lib/libfontconfig.so.1 (0x28c4c000) liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28c74000) libGLcore.so.1 = /usr/X11R6/lib/libGLcore.so.1 (0x28c8f000) ^^ What is this? Oh!!! This is library from nvidia driver. Nvidia driver replaces libGL.so and new libGL require libGLcore.so. After full deleting of nvidia driver port from system proglem is gone. Now licq works fine with libkse. Thanks! PS: How about new version of nvidia driver? How can I use nvidia driver and libkse on same machine? You probably can't safely. You'll have to wait for a new release of their driver, and hopefully they will have fixed the problem. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jail and emulators/linux_base
On Wed, Dec 03, 2003 at 10:22:16AM +0100, Niklas Saers Mailinglistaccount wrote: Hi all, I'm running CURRENT and set up a jail where I want to install SUN JDK 1.4.2. In the process, linux emulation needs to be installed. While installing emulators/linux_base, I get the following: === Installing for linux_base-7.1_5 Un-mounting linprocfs... umount: retrying using path instead of file system ID === Generating temporary packing list === Checking if emulators/linux_base already installed mknod: /compat/linux/dev/null: Operation not permitted *** Error code 1 While Linux-emulation is already up and running on the host-machine, it seems the jail is not allowed to create what it needs to run it. I understand allowing mknod(8) within a jail is dangerous in the case where you allow untrusted users to be root. Is there some way to either say I don't let untrusted users be root thus allowing this or to compile emulators/linux_base more jail-friendly, possibly setting things up from outside the jail? jail where I trust users not to try to take over my system = chroot. About compiles, btw, they seem to drag out forever in a jail. Especially configure takes ridiculous long time. I was under the impression that the overhead of running a jail should be very small, yet compiling shells/bash2 in a fresh jail took 8 minutes and 8.6 seconds while compiling it on the host system took 54.9 seconds. Are there options that may affect jail-performance I can tune? That's weird..it shouldn't be doing that. What scheduler are you running, what does top show, have you tried to trace the processes using ktrace, etc? Kris pgp0.pgp Description: PGP signature
Re: 40% slowdown with dynamic /bin/sh
On Wed, Dec 03, 2003 at 07:44:16AM -0600, Bob Willcox wrote: Nothing specific. I suppose it's just a space-time tradeoff from my point of view. With disk sizes what they are today (most of my systems have a system disk size of 40 GB or more), in my environment reducing the root filesystem size just isn't a priority. Don't use it then, and let the thread die. Kris pgp0.pgp Description: PGP signature
Re: jail and emulators/linux_base
Niklas Saers Mailinglistaccount [EMAIL PROTECTED] writes: === Installing for linux_base-7.1_5 Un-mounting linprocfs... umount: retrying using path instead of file system ID === Generating temporary packing list === Checking if emulators/linux_base already installed mknod: /compat/linux/dev/null: Operation not permitted *** Error code 1 man devfs DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, Dec 03, 2003 at 01:43:57PM +0200, Dan Naumov wrote: Hello What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am considering going back to it but I need to figure out how to prevent this issue from happening again. My system has 2 harddrives, a 16 GB Seagate that I use for backups and mount it under /mnt/backup and a 40 GB Maxtor that I am using for everything else. After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris pgp0.pgp Description: PGP signature
Re: -current lockup (how to diagnose?)
Robert Watson [EMAIL PROTECTED] writes: On Tue, 2 Dec 2003, Jun Kuriyama wrote: At Mon, 1 Dec 2003 09:23:21 -0500 (EST), Robert Watson wrote: This could be a sign of a VM or VFS lock leak or deadlock. I'd advise hooking up a serial console, dropping to DDB over serial line, and posting the results of ps and show lockedvnods. We might then ask you to use the show locks command on various processes. You'll need to have DDB and WITNESS compiled in. I got it. http://www.imgsrc.co.jp/~kuriyama/BSD/lock-20031202.log ouch Could you try compiling in DEBUG_LOCKS into your kernel and doing show lockedvnods with that? Unfortunately, someone removed the pid from the output of that command, but didn't add the thread pointer to the DDB ps output, so you'll probably need to modify the lockmgr_printinfo() function in vfs_subr.c to print out lkp-lk_lockholder-td_proc-p_pid as well for exclusive locks. It looks like maybe something isn't releasing a vnode lock before returning to userspace. I have some patches to assert that no lockmgr locks are held on the return to userspace, but I'll have to dig them up tomorrow and send them to you. Basically, it adds a per-thread lockmgr lock count in a thread-local variable, incrementing for each lock, and decrementing for each release, and then KASSERT()'s in userret that the variable is 0. I have the same problem. find is offending in my case: db ps pid proc uarea uid ppid pgrp flag stat wmesgwchan cmd 35331 c955654c f0bba0000 91902 35331 0004002 [SLP]getblk 0xd5782e3c] find 85666 c9556388 f0bb90000 86354 85666 0004002 [CV]select 0xc06d0b04] top 86354 c91a4710 ee7f50000 29327 86354 0004002 [SLP]pause 0xc9544000] csh 29327 c91a4e20 ee7f90000 40805 29327 100 [CV]select 0xc06d0b04] sshd 91902 c9385710 f0b540000 44297 91902 0004002 [SLP]pause 0xc9566000] csh 44297 c9273000 f0a460000 40805 44297 100 [CV]select 0xc06d0b04] sshd 89288 c92731c4 f0a8f0000 1 89288 0004002 [SLP]ttyin 0xc91ea010] getty 30656 c9557388 f0bc20000 1 30656 0004002 [SLP]ttyin 0xc93c4010] getty 23066 c8f1e710 e60d60000 1 23066 0004002 [SLP]ttyin 0xc92bfe10] getty 3582 c9557000 f0bc0 1 3582 0004002 [SLP]ttyin 0xc93c3210] getty 38198 c9273c5c f0a950000 1 38198 0004002 [SLP]ttyin 0xc93c3810] getty 32813 c95568d4 f0bbc0000 1 32813 0004002 [SLP]ttyin 0xc93c3e10] getty 25214 c9556a98 f0bbd0000 1 25214 0004002 [SLP]ttyin 0xc93c4410] getty 85142 c9231000 f09ea0000 1 85142 0004002 [SLP]ttyin 0xc91ea210] getty 27067 c9385e20 f0ba0 1 27067 0004002 [SLP]ttyin 0xc8fc1410] getty 89169 c955754c f0bc30000 1 89169 000 [SLP]nanslp 0xc06a971c] cron 40805 c9231710 f0a360000 1 40805 100 [CV]select 0xc06d0b04] sshd 13151 c92a1710 f0aff0000 1 13151 000 [CV]select 0xc06d0b04] syslogd 83 c91a3388 ee7c60000 0 0 204 [SLP]- 0xc06d312c] nfsiod 3 82 c91a354c ee7c70000 0 0 204 [SLP]- 0xc06d3128] nfsiod 2 81 c91a3710 ee7c80000 0 0 204 [SLP]- 0xc06d3124] nfsiod 1 80 c91a38d4 ee7c90000 0 0 204 [SLP]- 0xc06d3120] nfsiod 0 79 c91a3a98 ee7ca0000 0 0 204 [SLP]vlruwt 0xc91a3a98] vnlru 78 c91a3c5c ee7cb0000 0 0 204 [SLP]syncer 0xc06a90e0] syncer 77 c91a3e20 ee7cc0000 0 0 204 [SLP]psleep 0xc06d0f6c] bufdaen 76 c91a4000 ee7cd0000 0 0 20c [SLP]pgzero 0xc06d98e8] pagezeo 75 c8ee7a98 e60a20000 0 0 204 [SLP]psleep 0xc06d9940] vmdaemn 74 c8ee7c5c e60a30000 0 0 204 [SLP]psleep 0xc06d992c] pagedan 73 c8ee7e20 e60a40000 0 0 204 [IWAIT] swi0: tty:sio 9 c8f1b000 e60a50000 0 0 204 [SLP]aifthd 0xc8f1b000] aac0aif 8 c8f1b1c4 e60a60000 0 0 204 [SLP]actask 0xc06a0dcc] acpi_t2 7 c8f1b388 e60a70000 0 0 204 [SLP]actask 0xc06a0dcc] acpi_t1 6 c8f1b54c e60a80000 0 0 204 [SLP]actask 0xc06a0dcc] acpi_t0 72 c8f1b710 e60a90000 0 0 204 new [IWAIT] swi5:+ 5 c8f1b8d4 e60aa0000 0 0 204 [SLP]tqthr 0xc06aab68] taskquee 71 c8f1ba98 e60ab0000 0 0 204 new [IWAIT] swi6:+ 70 c8f1bc5c e60ac0000 0 0 204 [IWAIT] swi7: task queue 69 c8f1be20 e60ad0000 0 0 204 [IWAIT] swi7: acpitaskq 68 c8f1e000 e60ae0000 0 0 204 new [IWAIT] swi3: cambio 67 c8f1e1c4 e60af0000 0 0 204 new [IWAIT] swi2: camnet 66 c8f1e388 e60b0 0 0 204 [SLP]- 0xc06a1040] random 4 c8ed21c4 e604c0000 0 0 204 [SLP]- 0xc06a3d60] g_down 3 c8ed2388 e604d0000 0 0 204 [SLP]- 0xc06a3d5c] g_up 2 c8ed254c e604e0000 0 0 204 [SLP]- 0xc06a3d54] g_event 65 c8ed2710 e604f0000 0 0 204 [IWAIT] swi1: net 64 c8ed28d4
Re: [ATAng?] ad1 disappeared again
On Wed, Dec 03, 2003 at 09:55:56AM +0100, Soren Schmidt wrote:
It seems Chris Faulhaber wrote:
I have been seeing the same issue since August with a different,
but similiar, set of drives:
ad0: 57241MB ST360015A [116301/16/63] at ata0-master UDMA100
ad1: 57241MB ST360015A [116301/16/63] at ata0-slave UDMA100
Under -CURRENT only the first drive is seen; RELENG_4 still works
fine.
Could you try this patch and get back to me with the result please:
Works for me:
GEOM: create disk ad0 dp=0xc6972c60
ad0: 57241MB ST360015A [116301/16/63] at ata0-master UDMA100
GEOM: create disk ad1 dp=0xc6972b60
ad1: 57241MB ST360015A [116301/16/63] at ata0-slave UDMA100
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.23
diff -u -r1.23 ata-lowlevel.c
--- ata-lowlevel.c 2 Nov 2003 22:04:53 - 1.23
+++ ata-lowlevel.c 3 Dec 2003 07:50:44 -
@@ -575,7 +575,7 @@
}
}
}
- if (stat1 ATA_S_BUSY) {
+ if (!((mask == 0x03) (stat0 ATA_S_BUSY)) (stat1 ATA_S_BUSY)) {
ATA_IDX_OUTB(ch, ATA_DRIVE, ATA_D_IBM | ATA_SLAVE);
DELAY(10);
-S?ren
.. but it works under windows!!
--
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD: The Power To Serve - http://www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel SE7500WV2 not working with ACPI
On 02-Dec-2003 Brooks Davis wrote: On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote: On 25-Nov-2003 Brooks Davis wrote: Since the interrupt changes, my dual Xeons based on the SE7500WV2 board don't work with ACPI. Specificly, the onboard nics (em0 and em1) appear to not be recieving interupts. Instead, they continiously get watchdog timeouts. In a stock current, this is an instant panic. With a minor fix to the watchdog function, the system sees to be more or less funcitonal other then not having a network. Disabling ACPI makes the nics work. I have updated the BIOS to the latest version[0]. I've included ACPI and non-ACPI dmesg output below. What else is needed to diagnose this problem? Any patches I should try? Since acpi0 failed to probe, ACPI isn't used to route interrupts. However, the apic code expects ACPI to do that since it enumerated CPUs and I/O APICs. You are just going to have to disable ACPI for now. acpi0: INTEL SWV20on motherboard ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 0xc29b4660), AE_NOT_EXIST acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_probe_and_attach: acpi0 attach returned 6 If you can get this fixed, then you can re-enable ACPI again. What I can't figure out is why this is failing since acpi was at least partialy working before. For instance, soft power was definalty working. Doesn't that depend on acpi attaching? Yes. What does a dmesg from a UP kernel or a kernel w/o 'device apic' show? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ pgp0.pgp Description: PGP signature
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Brian F. Feldman wrote: Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 40% slowdown with dynamic /bin/sh
In a message written on Tue, Dec 02, 2003 at 06:05:40PM -0200, Daniel C. Sobral wrote: And if you are using FreeBSD on desktop you should use bash or some other ports-shell, instead of slowing down _the_ shell for shell scripts. But that's IMHO, so I didn't pipe this in until now. But it's the very same argument you are making, so I thought you deserved to hear it. Except that bash at least is linked statically in ports, supports none of this, and people don't seem to want to change it. Gotta love consistency. -- Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - [EMAIL PROTECTED], www.tmbg.org pgp0.pgp Description: PGP signature
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Kris Kennaway wrote You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris I usually discover that I am having data corruption when trying to update ports. A file that has a Bad File Descriptor refuses to let cvsup overwrite and/or remove itself. I've also had make installworld fail on me for the very same reason. A file in the base system would get corrupted and would prevent anything from overwriting itself. These problems would go away after a full system fsck, but the fsck would remove the damaged files completely, sometimes leaving the system in a severely broken state. And even if it did not, data corruption would happen again in 8-12 days. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Go ahead and load up kernel.debug and the core dump in gdb -k, and show us
the backtrace. Also, do you have any idea about more specific circumstances
that will cause this problem? Thanks!
Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch
I've applied patch.
Now it's a second fault.
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0xe5
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc053f1a8
stack pointer = 0x10:0xe62dbaac
frame pointer = 0x10:0xe62dbacc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 1851 (make)
trap number = 12
panic: page fault
cpuid = 2;
boot() called on cpu#2
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
cpuid = 2;
boot() called on cpu#2
Uptime: 2m55s
Dumping 2047 MB
[ skipped ]
---
#0 doadump () at ../../../kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc0517067 in boot (howto=260) at ../../../kern/kern_shutdown.c:372
#2 0xc0517480 in poweroff_wait (junk=0xc0666ee0, howto=-731617912)
at ../../../kern/kern_shutdown.c:550
#3 0xc05614e1 in bremfreel (bp=0xe62db71c) at ../../../kern/vfs_bio.c:647
#4 0xc05613eb in bremfree (bp=0x0) at ../../../kern/vfs_bio.c:629
#5 0xc0565de1 in getblk (vp=0xc814d000, blkno=131552, size=16384, slpflag=0,
slptimeo=0, flags=0) at ../../../kern/vfs_bio.c:2468
#6 0xc05615c2 in breadn (vp=0xc814d000, blkno=0, size=0, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at ../../../kern/vfs_bio.c:700
#7 0xc056156c in bread (vp=0x0, blkno=0, size=0, cred=0x0, bpp=0x0)
at ../../../kern/vfs_bio.c:682
#8 0xc05bba95 in ffs_update (vp=0xc896130c, waitfor=0)
at ../../../ufs/ffs/ffs_inode.c:108
#9 0xc05d1812 in ffs_fsync (ap=0xe62db91c) at ../../../ufs/ffs/ffs_vnops.c:325
#10 0xc05d06da in ffs_sync (mp=0xc811a800, waitfor=2, cred=0xc3f00e80,
td=0xc06a5ca0) at vnode_if.h:627
#11 0xc057ab8e in sync (td=0xc06a5ca0, uap=0x0)
at ../../../kern/vfs_syscalls.c:141
#12 0xc0516b75 in boot (howto=256) at ../../../kern/kern_shutdown.c:281
#13 0xc0517480 in poweroff_wait (junk=0xc066a837, howto=-1066983121)
at ../../../kern/kern_shutdown.c:550
#14 0xc0636d6c in trap_fatal (frame=0xc066a837, eva=0)
at ../../../i386/i386/trap.c:821
#15 0xc06363d3 in trap (frame=
{tf_fs = -1068105704, tf_es = -1037172720, tf_ds = -433258480, tf_edi =
-932123520, tf_esi = -1066740096, tf_ebp = -433210676, tf_isp = -433210728, tf_ebx =
-937236928, tf_edx = 0, tf_ecx = -931024576, tf_eax = -937236896, tf_trapno = 12,
tf_err = 0, tf_eip = -1068240472, tf_cs = 8, tf_eflags = 65666, tf_esp = -433210676,
tf_ss = -1068447965}) at ../../../i386/i386/trap.c:250
#16 0xc0623238 in calltrap () at {standard input}:94
#17 0xc053f984 in turnstile_wait (ts=0xc870ec80, lock=0xc06a94a0, owner=0x0)
at ../../../kern/subr_turnstile.c:510
#18 0xc050c655 in _mtx_lock_sleep (m=0xc06a94a0, opts=0, file=0x0, line=0)
at ../../../kern/kern_mutex.c:476
#19 0xc04ef50f in cv_timedwait_sig (cvp=0xc06adc64, mp=0xc06adc40, timo=0)
at ../../../kern/kern_condvar.c:478
#20 0xc0541972 in kern_select (td=0xc881b140, nd=20, fd_in=0xbfbfdbd0,
fd_ou=0x0, fd_ex=0x0, tvp=0xe62dbcd8) at ../../../kern/sys_generic.c:844
#21 0xc05412c6 in select (td=0x0, uap=0xe62dbd14)
at ../../../kern/sys_generic.c:720
#22 0xc0637120 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077945264, tf_esi = 134765696,
tf_ebp = -1077945256, tf_isp = -433209996, tf_ebx = 134895872, tf_edx = 2184, tf_ecx =
0, tf_eax = 93, tf_trapno = 22, tf_err = 2, tf_eip = 134628119, tf_cs = 31, tf_eflags
= 514, tf_esp = -1077945444, tf_ss = 47})
at ../../../i386/i386/trap.c:1010
#23 0xc062328d in Xint0x80_syscall () at {standard input}:136
---Can't read userspace from dump, or kernel process---
(kgdb)
Igor Sysoev
http://sysoev.ru/en/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Go ahead and load up kernel.debug and the core dump in gdb -k, and show us
the backtrace. Also, do you have any idea about more specific circumstances
that will cause this problem? Thanks!
It is SMP system 2xP4, HTT CPUs halted, 4BSD scheduler.
It panics sometimes when running in a cycle make -j 64 buildworld
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0xe5
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc053f197
stack pointer = 0x10:0xe3c21c80
frame pointer = 0x10:0xe3c21ca0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 42 (irq29: ahd0)
trap number = 12
panic: page fault
cpuid = 2;
boot() called on cpu#2
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
cpuid = 2;
boot() called on cpu#2
Uptime: 1d2h4m15s
Dumping 2047 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 1024 1040
1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312
1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584
1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 1824 1840 1856
1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032
---
#0 doadump () at ../../../kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc0517067 in boot (howto=260) at ../../../kern/kern_shutdown.c:372
#2 0xc0517480 in poweroff_wait (junk=0xc0666ee0, howto=-729086152)
at ../../../kern/kern_shutdown.c:550
#3 0xc05614d1 in bremfreel (bp=0xe3c218f0) at ../../../kern/vfs_bio.c:647
#4 0xc05613db in bremfree (bp=0x0) at ../../../kern/vfs_bio.c:629
#5 0xc0565dd1 in getblk (vp=0xc8154000, blkno=131360, size=16384, slpflag=0,
slptimeo=0, flags=0) at ../../../kern/vfs_bio.c:2468
#6 0xc05615b2 in breadn (vp=0xc8154000, blkno=0, size=0, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at ../../../kern/vfs_bio.c:700
#7 0xc056155c in bread (vp=0x0, blkno=0, size=0, cred=0x0, bpp=0x0)
at ../../../kern/vfs_bio.c:682
#8 0xc05bba85 in ffs_update (vp=0xc815330c, waitfor=0)
at ../../../ufs/ffs/ffs_inode.c:108
#9 0xc05d1802 in ffs_fsync (ap=0xe3c21af0) at ../../../ufs/ffs/ffs_vnops.c:325
#10 0xc05d06ca in ffs_sync (mp=0xc812a000, waitfor=2, cred=0xc3f00e80,
td=0xc06a5ca0) at vnode_if.h:627
#11 0xc057ab7e in sync (td=0xc06a5ca0, uap=0x0)
at ../../../kern/vfs_syscalls.c:141
#12 0xc0516b75 in boot (howto=256) at ../../../kern/kern_shutdown.c:281
#13 0xc0517480 in poweroff_wait (junk=0xc066a837, howto=-1066983121)
at ../../../kern/kern_shutdown.c:550
#14 0xc0636d5c in trap_fatal (frame=0xc066a837, eva=0)
at ../../../i386/i386/trap.c:821
#15 0xc06363c3 in trap (frame=
{tf_fs = -473825256, tf_es = -1068498928, tf_ds = -473825264, tf_edi =
-938141248, tf_esi = -1066743576, tf_ebp = -473817952, tf_isp = -473818004, tf_ebx =
-941495168, tf_edx = 0, tf_ecx = -941553792, tf_eax = -941495136, tf_trapno = 12,
tf_err = 0, tf_eip = -1068240489, tf_cs = 8, tf_eflags = 65667, tf_esp = -941551444,
tf_ss = 131}) at ../../../i386/i386/trap.c:250
#16 0xc0623228 in calltrap () at {standard input}:94
#17 0xc053f974 in turnstile_wait (ts=0xc81519c0, lock=0xc06a94a0, owner=0x0)
at ../../../kern/subr_turnstile.c:509
#18 0xc050c655 in _mtx_lock_sleep (m=0xc06a94a0, opts=0, file=0x0, line=0)
at ../../../kern/kern_mutex.c:476
#19 0xc0501405 in ithread_loop (arg=0xc7e05080)
at ../../../kern/kern_intr.c:543
#20 0xc0500040 in fork_exit (callout=0xc0501240 ithread_loop, arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:793
(kgdb) disassemble 0xc053f197
Dump of assembler code for function propagate_priority:
0xc053f070 propagate_priority:push %ebp
[ skipped ]
0xc053f0d7 propagate_priority+103:call 0xc052da60 sched_prio
0xc053f0dc propagate_priority+108:
jmp0xc053f2b2 propagate_priority+578
0xc053f0e1 propagate_priority+113:movzbl 0xfff0(%ebp),%eax
0xc053f0e5 propagate_priority+117:mov%al,0xe5(%ebx)
0xc053f0eb propagate_priority+123:mov0x60(%ebx),%edi
0xc053f0ee propagate_priority+126:mov0x24(%edi),%eax
0xc053f0f1 propagate_priority+129:shr$0x8,%eax
0xc053f0f4
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Brian F. Feldman wrote: Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch With this patch the system panics after short time when I run make -j 32 buildworld. I tried 2 times. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.0 boot beastie animation?
Just discovered a nice added leetness feature that makes the boot beastie be drawn in full color (loader_color=YES in loader.conf) ... ok seems leet ... but wouldn't it be even more leet when it would be drawn with the fork moving? One second with the fork 1 char space to left and then after a second char space to the original place where it is today (just 2 frames, and then redraw the beastie with one of them every second). We all boot our machines as seldom as possible, but let's make that booting FUN. Olev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Igor Sysoev wrote: On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Brian F. Feldman wrote: Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch I've applied patch. Now it's a second fault. This is the same fault. Did you just apply this patch today or did you apply an earlier version of it a while ago? I just updated it two days ago. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.0 boot beastie animation?
In message [EMAIL PROTECTED], Olev writes: Just discovered a nice added leetness feature that makes the boot beastie be drawn in full color (loader_color=YES in loader.conf) ... ok seems leet ... but wouldn't it be even more leet when it would be drawn with the fork moving? One second with the fork 1 char space to left and then after a second char space to the original place where it is today (just 2 frames, and then redraw the beastie with one of them every second). We all boot our machines as seldom as possible, but let's make that booting FUN. Just do not make it the default or people installing on serial consoles will hate you more than you imagine... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.0 boot beastie animation?
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Olev writes: Just do not make it the default or people installing on serial consoles will hate you more than you imagine... Ofcourse, just like you need to set loader_color=YES in loader.conf for colors, off by default. Olev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Igor Sysoev wrote: On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Brian F. Feldman wrote: Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch I've applied patch. Now it's a second fault. This is the same fault. Did you just apply this patch today or did you apply an earlier version of it a while ago? I just updated it two days ago. In [EMAIL PROTECTED] I sent trace before the patch. It seems to me that it's singe fault. Then I applied patch I saw the double fault. This trace I sent in [EMAIL PROTECTED]. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, Igor Sysoev wrote: On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Igor Sysoev wrote: On Wed, 3 Dec 2003, John Baldwin wrote: On 03-Dec-2003 Brian F. Feldman wrote: Igor Sysoev [EMAIL PROTECTED] wrote: I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to 2003.11.28.00.00.00 with the turnstile support and it can still causes sometimes a page fault in propogate_priority(). I have core dump and can send debug output. Go ahead and load up kernel.debug and the core dump in gdb -k, and show us the backtrace. Also, do you have any idea about more specific circumstances that will cause this problem? Thanks! Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch I've applied patch. Now it's a second fault. This is the same fault. Did you just apply this patch today or did you apply an earlier version of it a while ago? I just updated it two days ago. In [EMAIL PROTECTED] I sent trace before the patch. It seems to me that it's singe fault. Then I applied patch I saw the double fault. This trace I sent in [EMAIL PROTECTED]. Sorry, I missed your question. I've got and applied the patch today. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test pcm channel patch
On Dec 03, Sean Chittenden wrote: Hello All, Please test this PCM patch. It creates seperate locking classes for PCM channels and should prevent the warning where multiple mutexes from the same class are held (as reported recently). I believe this to be a good strategy as it masks fewer errors. I can confirm that this patch fixes my LOR for pcm(4). -sc Bah! I got 30min into playing tunes and picked the same LOR up not more than 5min after sending this. :( Sorry for the false alarm. acquiring duplicate lock of same type: pcm record channel 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144 2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146 Stack backtrace: Bah indeed. Gotta think some more. Thanks, --mat -- Any idiot can face a crisis; it is this day-to-day living that wears you out. - Chekhov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: User mounts could not use character conversions (libkiconv is just for roots)
On Wed, Dec 03, 2003 at 12:08:52PM +0600, Boris Popov wrote: Probably it is not a good idea to allow users to load kernel iconv tables because one can waste a lot of memory by loading of all possible conversion schemes. The better solution is to add some kind of preload ability which could be used on startup. I agree with this. - R. Imura ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ServeRAID semi show stopper (was Re: lots of exclusive sleep mutex)
Hi, Here comes more helpful ServeRAID related warnings: Bad malloc flags: 0 Stack backtrace: malloc() of 16 with the following non-sleepable locks held: exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @ /usr/src/sys/geom/geom_io.c:355 Bad uma_zalloc flags: 0 Stack backtrace: malloc() of 16 with the following non-sleepable locks held: exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @ /usr/src/sys/geom/geom_io.c:355 malloc() of 16 with the following non-sleepable locks held: exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @ /usr/src/sys/geom/geom_io.c:355 malloc() of 16 with the following non-sleepable locks held: exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @ /usr/src/sys/geom/geom_io.c:355 ( ... repeats ... ) The ServeRAID adaptor is # grep ips /var/run/dmesg.boot ips0: IBM ServeRAID Adapter mem 0xf000-0xf3ff irq 24 at device 1.0 on pci4 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ips0: adapter type: ServeRAID 5i II (sarasota) ips0: logical drives: 1 ips0: Logical Drive 0: RAID5 sectors: 142192640, state OK ipsd0: Logical Drive on ips0 GEOM: create disk ipsd0 dp=0xc6bc1010 ipsd0: Logical Drive (69430MB) To be more specific, it's FreeBSD 5.2-BETA with hint.acpi.0.disabled=1, running on IBM x225. Everything is ok, except the ServeRAID warns :) Clive ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test pcm channel patch
On Dec 03, Sean Chittenden wrote:
Hello All,
Please test this PCM patch. It creates seperate locking
classes for PCM channels and should prevent the warning where
multiple mutexes from the same class are held (as reported
recently). I believe this to be a good strategy as it masks fewer
errors.
I can confirm that this patch fixes my LOR for pcm(4). -sc
Bah! I got 30min into playing tunes and picked the same LOR up not
more than 5min after sending this. :( Sorry for the false alarm.
acquiring duplicate lock of same type: pcm record channel
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146
Stack backtrace:
Sean,
I found the mistake, I assumed that a variable was initialized
when it wasn't. Sorry for asking you to test a stupid patch before.
Please try this one.
Thanks again,
--Mat
--
Having your book made into a movie is like having your ox
made into a bouillon cube.
- Bill Neely
Index: channel.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pcm/channel.c,v
retrieving revision 1.92
diff -u -r1.92 channel.c
--- channel.c 27 Nov 2003 19:51:44 - 1.92
+++ channel.c 3 Dec 2003 16:55:41 -
@@ -67,9 +67,12 @@
static int chn_buildfeeder(struct pcm_channel *c);
static void
-chn_lockinit(struct pcm_channel *c)
+chn_lockinit(struct pcm_channel *c, int dir)
{
- c-lock = snd_mtxcreate(c-name, pcm channel);
+ if (dir == PCMDIR_PLAY)
+ c-lock = snd_mtxcreate(c-name, pcm play channel);
+ else
+ c-lock = snd_mtxcreate(c-name, pcm record channel);
}
static void
@@ -736,7 +739,7 @@
struct snd_dbuf *b, *bs;
int ret;
- chn_lockinit(c);
+ chn_lockinit(c, dir);
b = NULL;
bs = NULL;
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jail and emulators/linux_base
Hi, jail where I trust users not to try to take over my system = chroot. Thank you and Pawel Jakub Dawidek for pointing that out that possibility. Been living with jail-only thoughts for a little too long. ;) This solves my problem, although I don't totally agree as jail in addtion has an ip which makes it great for deploying test-setups. Using chroot only creates a need for workarounds. But hey, chrooting made me able to install the port and go from there. :) That's weird..it shouldn't be doing that. What scheduler are you running, what does top show, have you tried to trace the processes using ktrace, etc? I'm using the 4BSD scheduler. top is showing 95+% free, and systat agrees that idle is doing a great job. :) I've put a kdump at http://niklas.saers.com/kdump.log of compiling bash. I'm afraid I don't know how to go through it to determine what's slowing down the build compared to a ktrace from the host environment (http://niklas.saers.com/kdump2.log). Any suggestions? Cheers Nik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
PXE Boot with Beastie Menu
Has anyone got a working loader.rc for PXE booting Current with the Beastie menu etc. included? The one on freebsd.org is for 4.x machines, which works, but doesn't give you the ACPI options etc. Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ServeRAID semi show stopper (was Re: lots of exclusive sleep mutex)
Clive Lin wrote:
Hi,
Here comes more helpful ServeRAID related warnings:
Bad malloc flags: 0
Stack backtrace:
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
Bad uma_zalloc flags: 0
Stack backtrace:
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
( ... repeats ... )
The ServeRAID adaptor is
# grep ips /var/run/dmesg.boot
ips0: IBM ServeRAID Adapter mem 0xf000-0xf3ff irq 24 at device 1.0 on pci4
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ips0: adapter type: ServeRAID 5i II (sarasota)
ips0: logical drives: 1
ips0: Logical Drive 0: RAID5 sectors: 142192640, state OK
ipsd0: Logical Drive on ips0
GEOM: create disk ipsd0 dp=0xc6bc1010
ipsd0: Logical Drive (69430MB)
To be more specific, it's FreeBSD 5.2-BETA with
hint.acpi.0.disabled=1, running on IBM x225. Everything is ok, except
the ServeRAID warns :)
The patch below will silence this warning. However, the real solution
is a lot more complicated and will have to wait for after 5.2.
Scott
--- ips_commands.c 27 Nov 2003 08:37:36 - 1.7
+++ ips_commands.c 3 Dec 2003 17:26:28 -
@@ -165,7 +165,7 @@
void ips_start_io_request(ips_softc_t *sc, struct bio *iobuf)
{
- if(ips_get_free_cmd(sc, ips_send_io_request, iobuf, 0)){
+ if(ips_get_free_cmd(sc, ips_send_io_request, iobuf,
IPS_NOWAIT_FLAG)){
device_printf(sc-dev, no mem for command slots!\n);
iobuf-bio_flags |= BIO_ERROR;
iobuf-bio_error = ENOMEM;
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, Dec 03, 2003 at 05:43:13PM +0300, Igor Sysoev wrote:
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0xe5
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc053f197
stack pointer = 0x10:0xe3c21c80
frame pointer = 0x10:0xe3c21ca0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 42 (irq29: ahd0)
trap number = 12
panic: page fault
cpuid = 2;
boot() called on cpu#2
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
cpuid = 2;
boot() called on cpu#2
Uptime: 1d2h4m15s
Dumping 2047 MB
jmp0xc053f2b2 propagate_priority+578
0xc053f187 propagate_priority+279:cmp(%edi),%ebx
0xc053f189 propagate_priority+281:
je 0xc053f290 propagate_priority+544
0xc053f18f propagate_priority+287:mov0x24(%ebx),%eax
0xc053f192 propagate_priority+290:mov0x4(%eax),%eax
0xc053f195 propagate_priority+293:mov(%eax),%edx
[ FAULT ]
/usr/src/sys/kern/subr_turnstile.c:256
td1 = TAILQ_PREV(td, threadqueue, td_lockq);
if (td1-td_priority = pri) {
mtx_unlock_spin(tc-tc_lock);
continue;
}
0xc053f197 propagate_priority+295:movzbl 0xe5(%edx),%eax
0xc053f19e propagate_priority+302:cmp0xfff0(%ebp),%eax
0xc053f1a1 propagate_priority+305:
jle0xc053f290 propagate_priority+544
0xc053f1a7 propagate_priority+311:call 0xc051e650 critical_enter
0xc053f1ac propagate_priority+316:mov%fs:0x0,%edx
0xc053f1b3 propagate_priority+323:mov$0x4,%eax
0xc053f1b8 propagate_priority+328:lock cmpxchg %edx,0xc06ac7fc
0xc053f1c0 propagate_priority+336:sete %al
0xc053f1c3 propagate_priority+339:movzbl %al,%eax
0xc053f1c6 propagate_priority+342:test %eax,%eax
0xc053f1c8 propagate_priority+344:
jne0xc053f210 propagate_priority+416
0xc053f1ca propagate_priority+346:mov%fs:0x0,%edx
--
Slawa Olhovchenkov
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Go ahead and load up kernel.debug and the core dump in gdb -k, and show us
the backtrace. Also, do you have any idea about more specific circumstances
that will cause this problem? Thanks!
Actually, please try http://www.FreeBSD.org/~jhb/patches/turnstile.patch
I've applied patch.
Now it's a second fault.
This is the same fault. Did you just apply this patch today or did
you apply an earlier version of it a while ago? I just updated it
two days ago.
In [EMAIL PROTECTED] I sent trace before
the patch. It seems to me that it's singe fault.
Then I applied patch I saw the double fault. This trace I sent in
[EMAIL PROTECTED].
Both faults are a trap 12 page fault with a faulting va of 0xe5
because td1 is NULL in priority propagation. Try this change to
get a better cashdump that can be analyzed:
Index: subr_turnstile.c
===
RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v
retrieving revision 1.134
diff -u -r1.134 subr_turnstile.c
--- subr_turnstile.c12 Nov 2003 23:48:42 - 1.134
+++ subr_turnstile.c3 Dec 2003 17:48:02 -
@@ -254,6 +254,7 @@
}
td1 = TAILQ_PREV(td, threadqueue, td_lockq);
+ MPASS(td1 != NULL);
if (td1-td_priority = pri) {
mtx_unlock_spin(tc-tc_lock);
continue;
Then print 'td' and '*ts' in gdb from the priority_propagation()
frame and mail the output.
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ServeRAID semi show stopper (was Re: lots of exclusive sleep mutex)
On Wed, Dec 03, 2003 at 10:29:19AM -0700, Scott Long wrote:
Clive Lin wrote:
Hi,
Here comes more helpful ServeRAID related warnings:
Bad malloc flags: 0
Stack backtrace:
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
Bad uma_zalloc flags: 0
Stack backtrace:
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
malloc() of 16 with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
( ... repeats ... )
The patch below will silence this warning. However, the real solution
is a lot more complicated and will have to wait for after 5.2.
Scott
--- ips_commands.c 27 Nov 2003 08:37:36 - 1.7
+++ ips_commands.c 3 Dec 2003 17:26:28 -
@@ -165,7 +165,7 @@
void ips_start_io_request(ips_softc_t *sc, struct bio *iobuf)
{
- if(ips_get_free_cmd(sc, ips_send_io_request, iobuf, 0)){
+ if(ips_get_free_cmd(sc, ips_send_io_request, iobuf,
IPS_NOWAIT_FLAG)){
device_printf(sc-dev, no mem for command slots!\n);
iobuf-bio_flags |= BIO_ERROR;
iobuf-bio_error = ENOMEM;
Hi,
It helps a lot to reduce my serial console traffic :)
Now only few warns below appears under heavy disk access:
ipsd0: iobuf error 12
ips0: no mem for command slots!
Clive
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Both faults are a trap 12 page fault with a faulting va of 0xe5
because td1 is NULL in priority propagation. Try this change to
get a better cashdump that can be analyzed:
Index: subr_turnstile.c
===
RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v
retrieving revision 1.134
diff -u -r1.134 subr_turnstile.c
--- subr_turnstile.c12 Nov 2003 23:48:42 - 1.134
+++ subr_turnstile.c3 Dec 2003 17:48:02 -
@@ -254,6 +254,7 @@
}
td1 = TAILQ_PREV(td, threadqueue, td_lockq);
+ MPASS(td1 != NULL);
if (td1-td_priority = pri) {
mtx_unlock_spin(tc-tc_lock);
continue;
Then print 'td' and '*ts' in gdb from the priority_propagation()
frame and mail the output.
With a patch from http://www.FreeBSD.org/~jhb/patches/turnstile.patch
I can not even rebuild kernel. Can I add MPASS to sources from
2003.11.28.00.00.00 ?
Igor Sysoev
http://sysoev.ru/en/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, Dec 03, 2003 at 05:55:29PM +0200, Dan Naumov wrote: Kris Kennaway wrote You get that error from what command(s)? Have you tried with 5.2, which has a new ATA driver? Kris I usually discover that I am having data corruption when trying to update ports. A file that has a Bad File Descriptor refuses to let cvsup overwrite and/or remove itself. I've also had make installworld fail on me for the very same reason. A file in the base system would get corrupted and would prevent anything from overwriting itself. These problems would go away after a full system fsck, but the fsck would remove the damaged files completely, sometimes leaving the system in a severely broken state. And even if it did not, data corruption would happen again in 8-12 days. Are there any other console or system messages logged? It sounds like there should be some other error reported by the kernel before the userland command receives the EBADF. Kris pgp0.pgp Description: PGP signature
Strange pcm/network problem
Hi there, since I installed 5.2-BETA, I've got a very strange problem. Always when I'm listening to some music and start a network transfer, both the music and the transfer stop after some time. Nothing is being received or sent any more, and the following message appears a few times: bfe0: watchdog timeout -- resetting This goes on until I exit xmms. When I exit xmms, after a few seconds the network works again. There's no problem in receiving and sending data then. I was able to reproduce this with mpg123, it just stops playing and exits when data is being sent over the network. The problem also persists when I'm using my rl nic instead of the onboard bfe chip. I'm using sources from yesterday (2003-11-02) now and this problem still occurs, no matter if sound support is loaded with kldload or compiled into the kernel. Please tell me when you need more information. Peter Hofer Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-BETA #0: Tue Dec 2 17:52:22 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMNESIAC Preloaded elf kernel /boot/kernel/kernel at 0xc074c000. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2672.74-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 1073659904 (1023 MB) avail memory = 1037697024 (989 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f23c0 pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:29 INTA BIOS irq 5 pci_cfgintr: 0:29 INTB BIOS irq 9 pci_cfgintr: 0:29 INTC BIOS irq 9 pci_cfgintr: 0:31 INTA BIOS irq 9 agp0: Intel Generic host to PCI bridge mem 0xf000-0xf7ff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci_cfgintr: 1:0 INTA BIOS irq 5 pci1: display, VGA at device 0.0 (no driver attached) pci1: display at device 0.1 (no driver attached) pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB at device 29.2 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: PCIBIOS PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 bfe0: Broadcom BCM4401 Fast Ethernet mem 0xd580-0xd5801fff at device 5.0 on pci2 pci_cfgintr: 2:5 INTA routed to irq 4 bfe0: Ethernet address: 00:0c:6e:07:cf:c0 miibus0: MII bus on bfe0 bmtphy0: BCM4401 10/100baseTX PHY on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: RealTek 8139 10/100BaseTX port 0xa800-0xa8ff mem 0xd500-0xd5ff at device 12.0 on pci2 pci_cfgintr: 2:12 INTA routed to irq 4 rl0: Ethernet address: 00:30:bd:1b:81:12 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: multimedia, audio at device 31.5 (no driver attached) orm0: Option ROM at iomem 0xc-0xccfff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0401 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) unknown: PNP0c02 can't assign resources (port)
Re: /usr/ports/xll/XFree86-4
On Dec 02, Jamie Bowden wrote: I have a new machine that I've just installed 5.1-R on, and cvsup'd to -C. I'm attempting to build X, and am getting a core dump from rman during the process. I had this happen too. I did something really hack-ish to get around it (like delete that documentation or some other unspeakable hack.) Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. Eric -- -- Eric AndersonSystems Administrator Centaur Technology All generalizations are false, including this one. -- Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/ports/xll/XFree86-4
In the last episode (Dec 03), Mike Hunter said:
On Dec 02, Jamie Bowden wrote:
I have a new machine that I've just installed 5.1-R on, and cvsup'd
to -C. I'm attempting to build X, and am getting a core dump from
rman during the process.
I had this happen too. I did something really hack-ish to get around
it (like delete that documentation or some other unspeakable hack.)
The coredump is due to bugs in the rman command (which is installed by
the imake port, believe it or not). I submitted a bugreport on it in
July, and hopefully it will be in Xfree86 4.4.0. Installing the
textproc/rman port may mask the bug until then, or you can drop this
file into ports/devel/imake-4/files and rebuild imake.
--
Dan Nelson
[EMAIL PROTECTED]
--- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003
+++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003
@@ -4104,6 +4104,9 @@
}
}
break;
+case 0:
+ /* ignore */
+ break;
default: /* unknown escaped character */
sputchar(*p++);
}
@@ -4133,7 +4133,7 @@ source_out0(const char *pin, char end)
/* postpone check until after following character so catch closing tags */
if ((sI=4+1 plain[sI-1-1]==')') ||
/* (plain[sI-1]==' ' (q=strchr(plain,' '))!=NULL qplain[sI-1])) */
-(plain[sI-1]==' ' !isalnum(plain[sI-1-1]))) {
+(sI=2 plain[sI-1]==' ' !isalnum(plain[sI-1-1]))) {
/* regardless, flush buffer */
source_flush();
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Tom wrote: On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. My troubles were with the MegaRAID variant, I'm not sure about the others.. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. First - I hope you mean the cards are physically OUT of the machine - it seemed to me that if they had a logical disk configuration on the card, it would hang. Although, it sounds like your problem is different. Actually, it kind of sounds like it thinks you are doing the -p boot thing to check for keyboard and roll over to the serial port. Other than that, I'm out of ideas (doesn't take long for that to happen though!).. :( Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange pcm/network problem
Peter, I'm afraid I haven't a clue why this happens to you but please see my notes below. On Dec 03, Peter Hofer wrote: since I installed 5.2-BETA, I've got a very strange problem. Always when I'm listening to some music and start a network transfer, both the music and the transfer stop after some time. Nothing is being received or sent any more, and the following message appears a few times: bfe0: watchdog timeout -- resetting This goes on until I exit xmms. When I exit xmms, after a few seconds the network works again. There's no problem in receiving and sending data then. I was able to reproduce this with mpg123, it just stops playing and exits when data is being sent over the network. And dmesg then says pcm channel dead ? The problem also persists when I'm using my rl nic instead of the onboard bfe chip. I'm using sources from yesterday (2003-11-02) now and this problem still occurs, no matter if sound support is loaded with kldload or compiled into the kernel. No need to try compiling PCM in the kernel, klds should work exactly the same. I notice that your network cards, sound card and sio use IRQ 4, I also note that your aren't using acpi, what happens when you enable it? A brief look at the ich code reveals that it's flagged as mpsafe when it isn't, but since you are UP, I don't see this being the cause. I also vaguely remember that another OS had a note about certain corner cases missing interrupts but I don't think that should affect other irq handlers either. I really am stumped. If we can't figure this out, you always do a binary search to find the commit that caused it, though since I wouldn't likely do this myself, I wouldn't expect you to. Input from others warmly received :) --mat -- Any idiot can face a crisis; it is this day-to-day living that wears you out. - Chekhov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -current lockup (how to diagnose?)
I am guessing that some of the recent locking changes are causing the problem. Unfortunately I am on the road now through Jan 4th, so will not be in a position to look at it. Hopefully one of the folks working on getting the SMP pushed down through the filesystem (Jeff Roberson, John Baldwin, or Alan Cox) will have some idea what broke recently. I would try looking at which process holds the buffer lock that the find is trying to get. You can usually unravel the chain of locks to eventually find what pair of events lead to the deadlock. It definitely helps to have DEBUG_LOCKS compiled into your kernel. Kirk McKusick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on i386/i386
TB --- /home/des/tinderbox/CURRENT/i386/i386/lock: flock(): Resource temporarily unavailable TB --- ERROR: unable to lock sandbox ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: initiate_write_inodeblock_ufs2: already started
This error happens if things are not properly locked. As per my previous message, I am not able to look at it now, but am hoping that resolving some of the other races will solve this as well. Kirk McKusick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 lost connection
Hi Kelley. The lasts update made a big different on the driver but still with problems, I have incoming errors and Oerrs and encaptulation erros and that make me loss connection with the clients, Im testing with 34 linux clients, but when I change the wireless card on the AP for a simple prism card the problem is corrected, anyway I agreed with you about the driver is very solid and fast, but fixing this Errors will be GREAT!, I hope someone can fix this soon Regards Marcos Kelley Reynolds wrote: The ath driver has been very solid since the last update about 5 days ago.. no problems at all. through many walls and one floor, I get a solid 54mbs all the time. Although, there are instances where a 2.4ghz phone will turn on the same channel approximately and cause the speed to slow down... sometimes all the way to 2 mbs. Before he removed the ath debug output in the default config, you could see the wireless rate decreasing in the kernel logs. Regards, Kelley -- Marcos Biscaysaqu Systems Administrator ThePacific.Net Ltd. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable devices in -current / 5.2-BETA?
On Dec 02, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Scott Long [EMAIL PROTECTED] writes: : However, having a general mechanism for disabling newbus devices would be : really nice. Agreed. But today and 5.2 you lose. However, it isn't easy. What does disabled mean? Don't attach? Don't even probe? If you don't probe, then how do you know that the device is aac.0? If you do probe, then you get ISA probe routines called that can be 'destructive'. 2 cents from a newbie. Have a pci_null driver that uses a tunable to probe and match at a higher priority. You would have to know what you are looking for to avoid it, but for someone who knows what they are doing, it would work. Please don't shoot me for being stupid :) --mat -- The state has no business in the bedrooms of the nation. - Pierre Elliott Trudeau ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
The World and MIT krb5
Hello all, I have installed the MIT krb5 port. I installed this port and left KRB5_HOME=/usr/local (this is where I installed the port) in make.conf. I assumed that building the world would use this variable and link the world (ssh[d], telnet[d], login, ...) against the libraries installed by the port. That didn't seem to happen. I didn't want to define MAKE_KERBEROS5 in make.conf because I already installed the port and I thought that defining MAKE_KERBEROS5 would overwrite some of the port. 1) Are the worlds daemons written to link against kerberos (as apposed to the heimdal replacements replacing their traditional counterparts)? 2) If 1), is there a way to link the world against the port? If so, how? 3) If 2) is possible, is it a bad idea? 4) Are people that use the MIT kerberos port replacing their daemons (telnet [d], login, ftp[d]) with the ports versions with good success? I'd imagine that since the port is installed in /usr/local things might not work so great if /usr/local can't be accessed (because of mount failure, etc.) unless the daemons are statically linked (NO THIS IS NOT A THREAD ABOUT STATIC LINKING, THIS IS AN OBSERVATION ABOUT THIS PORT AND A POSSIBLE ANSWER TO 3). Regards, Galen Sampson __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The World and MIT krb5
On Wed, Dec 03, 2003 at 11:52:27AM -0800, Galen Sampson wrote: Hello all, snip [Note: I'm not sure that this should be in current@ rather than [EMAIL PROTECTED] 1) Are the worlds daemons written to link against kerberos (as apposed to the heimdal replacements replacing their traditional counterparts)? The MIT krb5 port includes it's own daemons. 4) Are people that use the MIT kerberos port replacing their daemons (telnet [d], login, ftp[d]) with the ports versions with good success? Yup. Or they're using the Heimdal daemons in the base system (as described in the handbook chapter on Kerberos 5). I prefer MIT myself, but that's largely because of unrelated benefits that may apply only in my situation. I'd imagine that since the port is installed in /usr/local things might not work so great if /usr/local can't be accessed (because of mount failure, etc.) unless the daemons are statically linked (NO THIS IS NOT A THREAD ABOUT STATIC LINKING, THIS IS AN OBSERVATION ABOUT THIS PORT AND A POSSIBLE ANSWER TO 3). I'm not sure what you're talking about here ... if the deamons are in /usr/local/, and the /usr/local isn't available, static linking isn't going to help :-) I tend to put them in /usr/local/krb5 so that I can control which application I get by default with creative $PATH ordering. -T -- From empirical experience, your Exchange admin needs to put down the crack pipe and open a window to disperse the fumes. - A.S.R. quote (Joe Thompson) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Both faults are a trap 12 page fault with a faulting va of 0xe5
because td1 is NULL in priority propagation. Try this change to
get a better cashdump that can be analyzed:
Index: subr_turnstile.c
===
RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v
retrieving revision 1.134
diff -u -r1.134 subr_turnstile.c
--- subr_turnstile.c12 Nov 2003 23:48:42 - 1.134
+++ subr_turnstile.c3 Dec 2003 17:48:02 -
@@ -254,6 +254,7 @@
}
td1 = TAILQ_PREV(td, threadqueue, td_lockq);
+ MPASS(td1 != NULL);
if (td1-td_priority = pri) {
mtx_unlock_spin(tc-tc_lock);
continue;
Then print 'td' and '*ts' in gdb from the priority_propagation()
frame and mail the output.
With a patch from http://www.FreeBSD.org/~jhb/patches/turnstile.patch
I can not even rebuild kernel. Can I add MPASS to sources from
2003.11.28.00.00.00 ?
Sure. I've reproduced a panic locally with turnstile.patch. I can't
get my box to get a crash dump though. The ata crash dump code seems
to have panicd. :( Just revert turnstile.patch for now.
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Igor Sysoev wrote:
On Wed, 3 Dec 2003, John Baldwin wrote:
On 03-Dec-2003 Brian F. Feldman wrote:
Igor Sysoev [EMAIL PROTECTED] wrote:
I'd cvsup'ed 5.1-CURRENT from 2003.11.04.02.02.00 up to
2003.11.28.00.00.00 with the turnstile support and it can still
causes sometimes a page fault in propogate_priority().
I have core dump and can send debug output.
Both faults are a trap 12 page fault with a faulting va of 0xe5
because td1 is NULL in priority propagation. Try this change to
get a better cashdump that can be analyzed:
Index: subr_turnstile.c
===
RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v
retrieving revision 1.134
diff -u -r1.134 subr_turnstile.c
--- subr_turnstile.c12 Nov 2003 23:48:42 - 1.134
+++ subr_turnstile.c3 Dec 2003 17:48:02 -
@@ -254,6 +254,7 @@
}
td1 = TAILQ_PREV(td, threadqueue, td_lockq);
+ MPASS(td1 != NULL);
if (td1-td_priority = pri) {
mtx_unlock_spin(tc-tc_lock);
continue;
Then print 'td' and '*ts' in gdb from the priority_propagation()
frame and mail the output.
With a patch from http://www.FreeBSD.org/~jhb/patches/turnstile.patch
I can not even rebuild kernel. Can I add MPASS to sources from
2003.11.28.00.00.00 ?
Ok, I've just updated turnstile.patch again. I was testing a bogus
condition in my earlier patch. :/ This patch has survived for a while
now on my test machine that was panic'ing with the earlier patch, so
try giving this patch a try against stock CVS sources and see if it
clears up all your panics. Thanks.
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On Wed, 3 Dec 2003, John Baldwin wrote: With a patch from http://www.FreeBSD.org/~jhb/patches/turnstile.patch I can not even rebuild kernel. Can I add MPASS to sources from 2003.11.28.00.00.00 ? Ok, I've just updated turnstile.patch again. I was testing a bogus condition in my earlier patch. :/ This patch has survived for a while now on my test machine that was panic'ing with the earlier patch, so try giving this patch a try against stock CVS sources and see if it clears up all your panics. Thanks. I added MPASS to sources from 2003.11.28.00.00.00 and since then the system made 3 builds of the world. I think it would panic tomorrow or so. I'll get crash dump and then try your new patch. Can I apply the new patch to sources from 2003.11.28.00.00.00 or I need to cvsup to more recent data ? Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problem, my VAIO won't come back from suspension
Hi Nate, On Tuesday 02 December 2003 23:34, Nate Lawson wrote: Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not, try disabling acpi and using apm(4) to suspend and resume. Normally that would be grand, but now that I've not compiled acpi into the kernel, I have no /dev/apm anymore as well. Even with acpi, I never got a /dev/apmctl so apmd never worked. I've read through devfs(5)/(8), but as far as I understand, it is the driver's responsibility to create the device and even if you could do it in userland, than it will just be a non-configured device. I've attached my kernel config and dmesg.boot. Is there anything I'm missing? PS: I can live without suspend2disk, but sleep state S1 does not shutdown my display as well, so I'm pretty much out of options. -- Melvyn === FreeBSD sarevok.idg.nl 5.2-BETA FreeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOACPI i386 === # vim600: tw=78 ts=8 sw=8 ai noet # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.393 2003/11/03 22:48:25 jhb Exp $ machine i386 cpu I686_CPU ident SAREVOK #To statically compile in device wiring instead of /boot/device.hints hints SAREVOK.hints #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options NFS_ROOT#NFS usable as /, requires NFSCLIENT options NTFS#NT File System options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. # Debugging for use in -current options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS options WITNESS #Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN#Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #device apic# I/O APIC # deviceacpi device isa device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd #
Re: ACPI problem, my VAIO won't come back from suspension
On Wed, 3 Dec 2003, Melvyn Sopacua wrote: On Tuesday 02 December 2003 23:34, Nate Lawson wrote: Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not, try disabling acpi and using apm(4) to suspend and resume. Normally that would be grand, but now that I've not compiled acpi into the kernel, I have no /dev/apm anymore as well. If you don't have acpi(4), then you need to add device apm to your kernel to enable apm(4) support. Even with acpi, I never got a /dev/apmctl so apmd never worked. I've read through devfs(5)/(8), but as far as I understand, it is the driver's responsibility to create the device and even if you could do it in userland, than it will just be a non-configured device. You can't use apmd with acpi(4). It has /dev/acpictl. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/ports/xll/XFree86-4
On Wed, 3 Dec 2003, Dan Nelson wrote:
In the last episode (Dec 03), Mike Hunter said:
On Dec 02, Jamie Bowden wrote:
I have a new machine that I've just installed 5.1-R on, and cvsup'd
to -C. I'm attempting to build X, and am getting a core dump from
rman during the process.
I had this happen too. I did something really hack-ish to get around
it (like delete that documentation or some other unspeakable hack.)
The coredump is due to bugs in the rman command (which is installed by
the imake port, believe it or not). I submitted a bugreport on it in
July, and hopefully it will be in Xfree86 4.4.0. Installing the
textproc/rman port may mask the bug until then, or you can drop this
file into ports/devel/imake-4/files and rebuild imake.
Installing /usr/ports/emulators/linux_compat seems to fix this. I have no
idea why, but I went ahead and installed it so I could install the Nvidia
X driver. After I did that (built and installed linux_compat and built
and installed the Nvidia driver), I went ahead and re-entered
x11/XFree86-4/ and did a make install again (mostly just looking for the
error so I could comment the lines out of the makefile), and it built and
installed (after I rebuilt and reinstalled imake-4, just on principle).
There's an odd dependency hiding in there somewhere.
Now I just have to figure out why X only believes this LCD is capable of
640x480 or 320x240 instead of the 1920x1600 it's actually capable of, so
back to -mobile I go.
Jamie Bowden
--
It was half way to Rivendell when the drugs began to take hold
Hunter S Tolkien Fear and Loathing in Barad Dur
Iain Bowen [EMAIL PROTECTED]
--- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003
+++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003
@@ -4104,6 +4104,9 @@
}
}
break;
+case 0:
+ /* ignore */
+ break;
default: /* unknown escaped character */
sputchar(*p++);
}
@@ -4133,7 +4133,7 @@ source_out0(const char *pin, char end)
/* postpone check until after following character so catch closing tags */
if ((sI=4+1 plain[sI-1-1]==')') ||
/* (plain[sI-1]==' ' (q=strchr(plain,' '))!=NULL qplain[sI-1])) */
-(plain[sI-1]==' ' !isalnum(plain[sI-1-1]))) {
+(sI=2 plain[sI-1]==' ' !isalnum(plain[sI-1-1]))) {
/* regardless, flush buffer */
source_flush();
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problem, my VAIO won't come back from suspension
On Wednesday 03 December 2003 21:57, Nate Lawson wrote: On Wed, 3 Dec 2003, Melvyn Sopacua wrote: On Tuesday 02 December 2003 23:34, Nate Lawson wrote: Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not, try disabling acpi and using apm(4) to suspend and resume. Normally that would be grand, but now that I've not compiled acpi into the kernel, I have no /dev/apm anymore as well. If you don't have acpi(4), then you need to add device apm to your kernel to enable apm(4) support. $ grep apm /sys/i386/conf/SAREVOK_NOACPI device apm [EMAIL PROTECTED]~ $ uname -v FreeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOACPI I noticed in my dmesg.boot: $ grep PNP /var/run/dmesg.boot unknown: PNP0303 can't assign resources (port) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0501 can't assign resources (port) unknown: PNP0401 can't assign resources (port) I hope that's not what I think it is :) Even with acpi, I never got a /dev/apmctl so apmd never worked. I've read through devfs(5)/(8), but as far as I understand, it is the driver's responsibility to create the device and even if you could do it in userland, than it will just be a non-configured device. You can't use apmd with acpi(4). It has /dev/acpictl. Thanx! -- Melvyn === FreeBSD sarevok.idg.nl 5.2-BETA FreeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOACPI i386 === pgp0.pgp Description: signature
Re: Strange pcm/network problem
A quick tought; perhaps you need to remove irq 5 from pccard.conf But... The problem also persists when I'm using my rl nic instead of the onboard bfe chip. ..maybe not. Try it. Dylan On 3 Dec 2003 at 20:04, Peter Hofer wrote: Hi there, since I installed 5.2-BETA, I've got a very strange problem. Always when I'm listening to some music and start a network transfer, both the music and the transfer stop after some time. Nothing is being received or sent any more, and the following message appears a few times: bfe0: watchdog timeout -- resetting This goes on until I exit xmms. When I exit xmms, after a few seconds the network works again. There's no problem in receiving and sending data then. I was able to reproduce this with mpg123, it just stops playing and exits when data is being sent over the network. The problem also persists when I'm using my rl nic instead of the onboard bfe chip. I'm using sources from yesterday (2003-11-02) now and this problem still occurs, no matter if sound support is loaded with kldload or compiled into the kernel. Please tell me when you need more information. Peter Hofer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange pcm/network problem
Mathew Kanner wrote: I notice that your network cards, sound card and sio use IRQ 4, I also note that your aren't using acpi, what happens when you enable it? You're right, it was because of ACPI ;) I just compiled a GENERIC kernel and booted it with ACPI ENABLED. The problem didn't occur. Then, I booted it with ACPI DISABLED, and the problem was there again. Thank you. Peter Hofer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange pcm/network problem
On Dec 03, Peter Hofer wrote: Mathew Kanner wrote: I notice that your network cards, sound card and sio use IRQ 4, I also note that your aren't using acpi, what happens when you enable it? You're right, it was because of ACPI ;) I just compiled a GENERIC kernel and booted it with ACPI ENABLED. The problem didn't occur. Then, I booted it with ACPI DISABLED, and the problem was there again. Good news, please supply a dmesg before and after. Thanks, --mat -- I don't even know what street Canada is on. - Al Capone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A page fault in subr_turnstile.c:propogate_priority()
On 03-Dec-2003 Igor Sysoev wrote: On Wed, 3 Dec 2003, John Baldwin wrote: With a patch from http://www.FreeBSD.org/~jhb/patches/turnstile.patch I can not even rebuild kernel. Can I add MPASS to sources from 2003.11.28.00.00.00 ? Ok, I've just updated turnstile.patch again. I was testing a bogus condition in my earlier patch. :/ This patch has survived for a while now on my test machine that was panic'ing with the earlier patch, so try giving this patch a try against stock CVS sources and see if it clears up all your panics. Thanks. I added MPASS to sources from 2003.11.28.00.00.00 and since then the system made 3 builds of the world. I think it would panic tomorrow or so. I'll get crash dump and then try your new patch. Can I apply the new patch to sources from 2003.11.28.00.00.00 or I need to cvsup to more recent data ? New patch should probably work fine with those sources. If you still get panics, you can try removing the extra MPASS(), and applying turnstile2.patch. It adds some debugging printf's that would be very helpful in tracking down the bug. Thanks. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel SE7500WV2 not working with ACPI
Brooks Davis wrote: Since acpi0 failed to probe, ACPI isn't used to route interrupts. However, the apic code expects ACPI to do that since it enumerated CPUs and I/O APICs. You are just going to have to disable ACPI for now. acpi0: INTEL SWV20on motherboard ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 0xc29b4660), AE_NOT_EXIST acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_probe_and_attach: acpi0 attach returned 6 If you can get this fixed, then you can re-enable ACPI again. What I can't figure out is why this is failing since acpi was at least partialy working before. For instance, soft power was definalty working. Doesn't that depend on acpi attaching? I plan on updating our ACPI-CA to the 20031202 dist after the code freeze is over. It has some important fixes, including this one: --- Changed the initialization of Operation Regions during subsystem init to perform two entire walks of the ACPI namespace; The first to initialize the regions themselves, the second to execute the _REG methods. This fixed some interdependencies across _REG methods found on some machines. --- You might be able to work around this problem by setting: debug.acpi.disable=ec or debug.acpi.avoid=\_SB_.PCI0.SBRG -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAPI CD still not detected, verbose boot logs available
On Wednesday 03 December 2003 09:55, Soren Schmidt wrote:
Could you try this simple patch and see if that helps?
Works for me. No problems so far during three reboots.
Log files available at
http://cheasy.dyndns.org/bootlogs/5.1-2003-11-30-patched/
Thanks for the good work!
-Christoph Sold
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.23
diff -u -r1.23 ata-lowlevel.c
--- ata-lowlevel.c 2 Nov 2003 22:04:53 - 1.23
+++ ata-lowlevel.c 3 Dec 2003 07:50:44 -
@@ -575,7 +575,7 @@
}
}
}
- if (stat1 ATA_S_BUSY) {
+ if (!((mask == 0x03) (stat0 ATA_S_BUSY)) (stat1
ATA_S_BUSY)) {
ATA_IDX_OUTB(ch, ATA_DRIVE, ATA_D_IBM | ATA_SLAVE);
DELAY(10);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Dan Naumov wrote: What follows is a description of a problem I used to have when running FreeBSD 5.0 and 5.1. [...] After the installation of the OS (usually about 8-12 days of running non-stop) I start getting Bad File Descriptor errors on random files all around the Maxtor drive and I have to go to single-user mode in order to run a full fsck on the system. After that, the system works, until in 8-12 days time even more files get corrupted this way and the process has to be repeated. Eventually, so many files are damaged that a full OS reinstall is required. I had exactly the same experiences while using the same FreeBSD versions. The filesystems slowly died without any direct sign pointing to hardware problems. But, after having exchanged the harddisk with a newer one, the effect never occured again. k.j. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAPI CD still not detected, verbose boot logs available
V st, 03. 12. 2003 v 22:39, Christoph Sold pe: On Wednesday 03 December 2003 09:55, Soren Schmidt wrote: Could you try this simple patch and see if that helps? Works for me. No problems so far during three reboots. Me too! My second Seagate drive is back and running. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?=
Re: Strange pcm/network problem
Good news, please supply a dmesg before and after. I've attached them. Both are GENERIC kernels, one booted with ACPI ENABLED [default] and the other with ACPI DISABLED. Thanks for your help, Peter Hofer Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-BETA #1: Wed Dec 3 21:42:28 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0a78000. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2672.74-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 1073659904 (1023 MB) avail memory = 1033498624 (985 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f23c0 pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:29 INTA BIOS irq 5 pci_cfgintr: 0:29 INTB BIOS irq 9 pci_cfgintr: 0:29 INTC BIOS irq 9 pci_cfgintr: 0:31 INTA BIOS irq 9 agp0: Intel Generic host to PCI bridge mem 0xf000-0xf7ff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci_cfgintr: 1:0 INTA BIOS irq 5 pci1: display, VGA at device 0.0 (no driver attached) pci1: display at device 0.1 (no driver attached) uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xb800-0xb81f irq 5 at device 29.0 on pci0 usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xb400-0xb41f irq 9 at device 29.1 on pci0 usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xb000-0xb01f irq 9 at device 29.2 on pci0 usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ugen0: Microsoft Microsoft SideWinder game controller, rev 1.00/0.95, addr 2 pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: PCIBIOS PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 bfe0: Broadcom BCM4401 Fast Ethernet mem 0xd580-0xd5801fff at device 5.0 on pci2 pci_cfgintr: 2:5 INTA routed to irq 4 bfe0: Ethernet address: 00:0c:6e:07:cf:c0 miibus0: MII bus on bfe0 bmtphy0: BCM4401 10/100baseTX PHY on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: RealTek 8139 10/100BaseTX port 0xa800-0xa8ff mem 0xd500-0xd5ff at device 12.0 on pci2 pci_cfgintr: 2:12 INTA routed to irq 4 rl0: Ethernet address: 00:30:bd:1b:81:12 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: multimedia, audio at device 31.5 (no driver attached) orm0: Option ROM at iomem 0xc-0xccfff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0401 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0f13 can't assign resources
5.2-BETA: IA32 SMP: atkbd gone, lock order reversal swap_pager/uma_core
I have made some experiences on a Fujitsu-Siemens Primergy RX300 (Serverworks, Xeon with HyperThreading, MegaRAID) today. I was able to boot the 5.2-BETA ISO from CD-RW after being unsuccessful with floppies yesterday (not that I'd particularly trust floppies...) Here's what I've found so far: 1. KEYBOARD LOST I need to explicitly escape to the loader prompt and set hint.atkbd.0.flags=0 -- with the default of 0x1, I am unable to use the keyboard (tried twice, without and with re-plugging the keyboard, to no avail). The exact reason is unknown, the machine has remote management hardware on board which might interfere. Can this flags=0 be made the default or would that interfere with USB keyboard and headless configurations? 2. LOCK ORDER REVERSAL I let the machine buildworld, build a kernel and cvsup ports+doc at the same time through screen. Both buildworld and the kernel make were launched with -j2. The machine then caught a LOR, but it may have happened after these tasks completed, neither make nor the cvsup reported an error. Here's the dmesg: FreeBSD 5.2-BETA #0: Tue Nov 25 08:24:08 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0a76000. ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.13-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 536870912 (512 MB) avail memory = 511750144 (488 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ... SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/amrd0s4a ... Lock order reversal 1st 0xc55acdec vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 2nd 0xc098cf60 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 3rd 0xc10398c4 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:876 Stack backtrace: (no backtrace) Since then, no further problems have been logged in the past three and a half hours. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vm_fault on umass transfers
Alastair G. Hogge wrote this message on Mon, Nov 10, 2003 at 20:02 +1100: I've had an Olympus camera which I've been able to access under -CURRENT for some time until recently. I can mount_msdosfs the device (da0s1) OK, but when I try to copy or move files from the device to my hard disk drive I get the following kernel message: panic: mv_fault: fault on nofault entry, addr: dc346000 And then the system will start to shutdown and sync disks. Unfortunately I've been unable to boot with a generic kernel at this stage to see if there would be more information spat out. Sorry for the long delay, finally getting to the -current list after a trip. Is this on ochi? There was a patch that might have fixed thigh committed recently. Is this still reproducable on -current? Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
On Wed, 3 Dec 2003, Dan Naumov wrote: causing this bizarre behavior ? If this is of any help, the exact model number of the HD is MAXTOR 4K040H2 and I was using UFS2 on both drives. Thanks in advance. Maxtor has a diag tool that goes onto a floppy that you could run. I have this exact disk in my sparc64 here and the first time I used it, it kept running over bad sectors and generally causing mayhem. Running the full scan with the tool, it prompted to fix some problems, then the bad sectors went away. I reinstalled the OS to clear out the broken files and I never had any problems afterward. The program is called PowerMax and is available from the downloads section under either diagnostics or utilities. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXE Boot with Beastie Menu
On Wed, 3 Dec 2003, Lawrence Farr wrote: Has anyone got a working loader.rc for PXE booting Current with the Beastie menu etc. included? The one on freebsd.org is for 4.x machines, which works, but doesn't give you the ACPI options etc. eh? The beastie menu ships by default on 5.X. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Wed, 3 Dec 2003, Tom wrote: On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. 1550 = lsi megaraid 1650 = adaptec 1750 = lsi megaraid 2550 = adaptec ( don't know the 2650 card just know ). perc stands for poweredge raid controller, so perc just means dell raid card nothing more nothing less. And with the dell habit of switching vendors every model that ain't very informative. -- Sten Spans There is a crack in everything that's how the light gets in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.x and Bad File Descriptor errors. Why?
Doug White wrote: Maxtor has a diag tool that goes onto a floppy that you could run. I have this exact disk in my sparc64 here and the first time I used it, it kept running over bad sectors and generally causing mayhem. Running the full scan with the tool, it prompted to fix some problems, then the bad sectors went away. I reinstalled the OS to clear out the broken files and I never had any problems afterward. The program is called PowerMax and is available from the downloads section under either diagnostics or utilities. I've tried running PowerMax on the drive with a through scan but no errors were found. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault panic -CURRENT
I'm still able to reproduce this panic today. As well as general flakyness
on the CD drive on -CURRENT. Had my first bad burn with this drive today.
Can't mount some cds that I just burned with the drive, yet mounts fine in
my 4.9 system. Can't seem to burn multisession disks, etc. Anyone else
seeing this?
Dec 4 00:56:22 littleguy kernel: acd0: FAILURE - CLOSE_TRACK/SESSION
status=51READY,DSC,ERROR sensekey=ILLEGAL REQUEST error=0
Dec 4 00:57:15 littleguy kernel: acd0: FAILURE - CLOSE_TRACK/SESSION
status=51READY,DSC,ERROR sensekey=ILLEGAL REQUEST error=0
On Friday 28 November 2003 06:12 pm, Anish Mistry wrote:
I'm getting a repeatable panic when try to access my cdrom drive.
-CURRENT as
of yesterday. I seem to get this when I try to mount my cdrom drive a
second
time.
I seem to get these error sometimes when trying to mount a cd for the
first
time and it doesn't end up work, and the second time I get the panic.
acd0: FAILURE - READ_CD status=51READY,DSC,ERROR sensekey=MEDIUM ERROR
error=0
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04f8a59 in boot (howto=256) at /usr/src/sys/kern/
kern_shutdown.c:372
#2 0xc04f8e38 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc0613fc6 in trap_fatal (frame=0xcdb1cc44, eva=0)
at /usr/src/sys/i386/i386/trap.c:821
#4 0xc0613c62 in trap_pfault (frame=0xcdb1cc44, usermode=0, eva=28)
at /usr/src/sys/i386/i386/trap.c:735
#5 0xc061379d in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi =
-1031146752,
tf_
ebp = -843985768, tf_isp = -843985808, tf_ebx = -1031197888, tf_edx = 0,
tf_ecx
= -1066906236, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip =
-1068409245,
tf_
cs = 8, tf_eflags = 66055, tf_esp = -843985744, tf_ss = -1068781253})
at /usr/src/sys/i386/i386/trap.c:420
#6 0xc0604898 in calltrap () at {standard input}:94
#7 0xc04bfad8 in g_destroy_provider (pp=0xc2892b40)
at /usr/src/sys/geom/geom_subr.c:426
#8 0xc04bcaa5 in g_orphan_register (pp=0xc289f300)
at /usr/src/sys/geom/geom_event.c:143
#9 0xc04bcbcc in one_event () at /usr/src/sys/geom/geom_event.c:169
#10 0xc04bcdf5 in g_run_events () at /usr/src/sys/geom/geom_event.c:202
#11 0xc04bde05 in g_event_procbody () at /usr/src/sys/geom/
geom_kern.c:134
#12 0xc04e1700 in fork_exit (callout=0xc04bdde0 g_event_procbody,
arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:793
--
Anish Mistry
pgp0.pgp
Description: signature
