newpcm
would everyone who currently has an issue outstanding with newpcm please report it to me in the next few days directly, please, so i can get an idea of what needs work before release. i need as much detail as possible. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
Hello again No, my problem is not ahc related. This single processor system doesn't have any scsi It's a : PPro200/64MbRAM/8.4QuantumIDE/IntelVS440FX/Pioneer12x(which is not detected after upgraded to -CURRENT)/Digital 21240 (de0)/S3 Virge What I have in common with Christian is that it hangs during high usage, as I mentioned in my first post (e.g. compiling something, buildworld). I performed a buildworld this night with yesterday's code (in a common console) and it worked ok. I ONLY noticed this when having high CPU usage (e.g. compiling mysql port) when in using X. I am not saying this is X related. Common point here seems to be a busy system Joao Quoting "Dave J. Boers" [EMAIL PROTECTED]: On Mon, Jan 10, 2000 at 04:10:37AM +0100, Christian Carstensen wrote: this runs stable for 3 hours now... try a current kernel (checked out 4 hours ago), using a version of the file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by any means stable, but works better than everything else within the last 24 hours. Actually, I've booted a kernel from just before newyear (28 december) which works _reasonably_ fine (although it's the same kernel that gave me the lockup earlier) with a userland of today. Problem is that the lockups (I think) are ahc-related and my SCSI hard drive did refuse to come online on one or two occasions while booting the system cold... I therefore concluded that it might be a problem with the hardware. Now (with the new kernel) I find the scsi system unstable and I have doubts again. One piece of information might also be useful in this context. After the system lockup I sort of benchmarked the scsi performance by doing "dd if=/dev/zero of=./testfile bs=100 count=128" (actually I varied the blocksize) and got a _very poor_ performance of only 4 Mb/sec (which is usually around 10 to 12 Mb/sec). I isolated my drive to be the only scsi device and I even clocked the SCSI bus down from 20 Mhz to 8 Mhz, but to no avail. In the mean time, I disconnected my scsi hard drive and I am running from my IDE disk. --- Powered by Webvolution Networks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
On Mon, 10 Jan 2000, Joao Pedras wrote: What I have in common with Christian is that it hangs during high usage, as I mentioned in my first post (e.g. compiling something, buildworld). this is funny: the system operates well, even when on heavy load (especially disk load), until i want a little more 8). to become more precisely, a cvs checkout or make world is no problem, if - and that's really interesting - nothing else requests the system's attention. i've had some successfully reproducable crashes when generating much i/o usage (cvs, buildworld), which in fact caused no problem, and then simply starting pine. at the moment, pine opened the mail folder, all my noisy hard disks stopped and it was perfectly quiet apart from cpu fans. -- Christian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
On Mon, Jan 10, 2000 at 03:35:47PM +0100, Christian Carstensen wrote: this is funny: the system operates well, even when on heavy load (especially disk load), until i want a little more 8). to become more precisely, a cvs checkout or make world is no problem, if - and that's really interesting - nothing else requests the system's attention. i've had some successfully reproducable crashes when generating much i/o usage (cvs, buildworld), which in fact caused no problem, and then simply starting pine. at the moment, pine opened the mail folder, all my noisy hard disks stopped and it was perfectly quiet apart from cpu fans. That sounds exactly like the very dead state I found my system in when it hang (I only have one occurence, so far, but my system isn't under very heavy load lately). Make -j 9 buildworld completes fine. The hang seems to have occured during a simple 20 Mb transfer of email data from my ide to my scsi disk (which is a very short but i/o intensive operation). There might have been an incoming email at the same time. I will try an idiotic buildworld -j 30 this evening just to see wether I can hang the system reproducibly. Have to go now, however. Regards, Dave Boers. -- Fatal error: replace user and try again. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: __sigisempty() undefined if cc -g used.
On 10 Jan, Bruce Evans wrote:
Better yet: DEBUG_FLAGS=-g
Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in
bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included
A few verbose module makefiles add it explicitly. You can also use
COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel
Makefiles.
Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the
kernel with debug information? What about "config -g MYKERNEL"?
Do we really need a global debug option which covers everything?
If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a
bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's),
right? So we only have to make the KLD's consistent to the kernel (or am
I missing something):
bsd.kmod.mk:
---snip---
92c92
CFLAGS+= ${COPTS} -D_KERNEL ${CWARNFLAGS}
---
CFLAGS+= ${DEBUG} -D_KERNEL ${CWARNFLAGS}
---snip---
Bye,
Alexander.
--
Happy new year and no Y2K-crash to everyone.
http://www.Leidinger.net Alexander+Home @ Leidinger.net
Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
In message [EMAIL PROTECTED] , Christian Carstensen writes: On Mon, 10 Jan 2000, Joao Pedras wrote: What I have in common with Christian is that it hangs during high usage, as I mentioned in my first post (e.g. compiling something, buildworld). this is funny: the system operates well, even when on heavy load (especially disk load), until i want a little more 8). I have a make world hanging here: 0 19914 19902 169 -2 0 1276 932 getblk D+p10:00.09 yacc -d -o c-parse.c c-parse.y -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mouse problem(please help)
I install FreeBSD3.3 but i face a problem to config mouse in Xwindows. I'm not able to subscribe in freebsd-question so i send it here please solve this problem. I have a GENIUS mouse , port : com 2 (/dev/cuaa1). when i install FreeBSD that time i test my mouse and it's work that time but when i start "startx" mouse not working . Again i run XF86Setup program ,I also choose "mouse system , sysmouse" and port /dev/cuaa1 or /dev/sysmouse but no work. please help me how can i work mouse in Xwindows. please give me suggestion. satyajit To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Buildworld fails
With CURRENT-sources updates within an hour ago ... buildworld fails: cd /usr/src/gnu/lib/libdialog; make beforeinstall sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/gnu/lib/libdial og/dialog.h /usr/obj/usr/src/i386/usr/include sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/gnu/lib/libdia log/TESTS/Makefile /usr/obj/usr/src/i386/usr/share/examples/libdialog install: mkstemp: /usr/obj/usr/src/i386/usr/share/examples/INS@0244 for /usr/obj /usr/src/i386/usr/share/examples/libdialog: No such file or directory *** Error code 71 Stop in /usr/src/gnu/lib/libdialog. *** Error code 1 -- Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pppctl/ppp bug
Hi, I've noticed that pppctl hangs 100% repeatable when I'm doing "set log local +chat" followed by the "dial" command over diagnostic socket. In the case when the "dial" command being sent over other socket this behaviour doesn't observed. Following I'm attaching transcript of my sessions -Maxim Bad: Script started on Mon Jan 10 16:55:21 2000 bash-2.03$ pppctl 3000 ppp ON vega set log local +chat +phase ppp ON vega dia [doesn't respond to any keystroke other than ^C] ^C bash-2.03$ exit Script done on Mon Jan 10 16:55:53 2000 Good: Script started on Mon Jan 10 17:01:15 2000 bash-2.03$ pppctl 3000 ppp ON vega set log local +phase +chat ppp ON vega Phase: Connected to client from 127.0.0.1:53000 Phase: bundle: Establish Phase: deflink: closed - opening Phase: deflink: Connected! Phase: deflink: opening - dial Phase: Phone: 9-238 Chat: deflink: Dial attempt 1 of 20 Chat: Send: ATZ Chat: Expect(4): OK Chat: Received: ATDT9238- ATZ Chat: Received: OK Chat: Send: ATDT9238- Chat: Expect(45): CONNECT Chat: Received: ATDT9238- Chat: Received: BUSY Warning: Chat script failed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current hangs in make world (softupdates on ccd on ata)
Make world hangs reliably for me right now: + |... |/* starting time is 16:18:8 */ |/* ending time is 16:18:8 */ |ln -sf gxx-hash.h hash.h |echo '#include "cp/cp-tree.def"' gencheck.h |echo '#include "objc/objc-tree.def"' gencheck.h |sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" |/syv/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in c-parse.y |yacc -d -o c-parse.c c-parse.y + 0 19921 1 83 -2 0 1276 932 getblk D p00:00.09 yacc -d -o c-parse.c c-parse.y This is a softupdates filesystem on a ccd on ata... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Neomagic Sounddriver hangs HP OB4150
Hello, as someone already has mentioned for another Laptop, the new Neomagic Audio-Driver (btw. thank you for creating one) hangs my HP Omnibook 4150 during boot. The Laptop is equipped with the following Neomagic-Chip: chip1: NeoMagic MagicMedia 256AX Audio controller irq 10 at device 0.1 on pci1 The Stack-Backtrace looks exactly the same as the other mail mentioned. A little bit further digging into this shows me that on this Laptop every read access to the second memory-area of the chip in the range of 0x600-0x8ff brings the machine to a halt. I can read successfully from the areas with offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O Area starts at offset 0x600. This access brings the machine to a halt during boot. Any suggestions of what I could try? Michael ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender),Rainer Erlat, Hans-Joachim Lueckefett,Heribert Schmitz,Fritz Schuller ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: __sigisempty() undefined if cc -g used.
On Mon, 10 Jan 2000, Alexander Leidinger wrote:
On 10 Jan, Bruce Evans wrote:
Better yet: DEBUG_FLAGS=-g
Except it only supported in bsd.prog.mk and bsd.lib.mk, but not in
bsd.kmod.mk, kernel Makefiles, or if no bsd .mk files are included
A few verbose module makefiles add it explicitly. You can also use
COPTS, but it is only supported in bsd.prog.mk, bsd.kmod.mk and kernel
Makefiles.
Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the
kernel with debug information? What about "config -g MYKERNEL"?
DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL"
is the only correct way to set it. "makeoptions DEBUG=-g" is a hackish
way to set it. It depends on knowing the the Makefiles' internals.
Do we really need a global debug option which covers everything?
It's simpler to have the same global debug option for everything.
If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a
bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's),
right?
No. DEBUG is quite different.
So we only have to make the KLD's consistent to the kernel (or am
I missing something):
bsd.kmod.mk:
---snip---
92c92
CFLAGS+= ${COPTS} -D_KERNEL ${CWARNFLAGS}
---
CFLAGS+= ${DEBUG} -D_KERNEL ${CWARNFLAGS}
---snip---
This would break COPTS :-). All places should use something more like:
CFLAGS+=[-D_KERNEL] ${CWARNFLAGS} ${COPTS} ${DEBUG_FLAGS}
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Anonymity, was: load spike strangeness
On Sun, 9 Jan 2000, Leif Neland wrote: While I do not agree with your idea of need of anonymity, I respect your need for it. Could you not, instead of using the handle "FreeBSD", which sortof already is taken :-), just assume a human name? The use of an obviously not human name makes it uncomfortable to communicate with you. If you would call you John Smith, or Thomas Jefferson if you want, you could much more easily hide your (hideous?) precence in the lists. Please? Yeah, like Mr. K. :) Leif K To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: __sigisempty() undefined if cc -g used.
On 11 Jan, Bruce Evans wrote:
Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the
kernel with debug information? What about "config -g MYKERNEL"?
DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL"
If I set DEBUG in make.conf it should work, right? So what's private
about it?
is the only correct way to set it. "makeoptions DEBUG=-g" is a hackish
way to set it. It depends on knowing the the Makefiles' internals.
Do we really need a global debug option which covers everything?
It's simpler to have the same global debug option for everything.
We have CFLAGS (userland) and COPTFLAGS (kernel) in make.conf, shouldn´t
we also have e.g. DEBUG_FLAGS and DEBUG_KERNEL (renamed DEBUG from
above)?
Together with CFLAGS and COPTFLAGS it would make more sense, IMO.
And what about those people who want to compile only the kernel and the
KLD's with debug information, but not the userland?
If I read it correcly we have DEBUG_FLAGS for the userland (if it uses a
bsd.{prog,lib}.mk) and DEBUG for the kernel (and COPTS for KLD's),
right?
No. DEBUG is quite different.
Sorry, but I didn´t get the point. Is it a semantic difference or a
technical one?
So we only have to make the KLD's consistent to the kernel (or am
I missing something):
bsd.kmod.mk:
---snip---
92c92
CFLAGS+= ${COPTS} -D_KERNEL ${CWARNFLAGS}
---
CFLAGS+= ${DEBUG} -D_KERNEL ${CWARNFLAGS}
---snip---
This would break COPTS :-). All places should use something more like:
CFLAGS+= [-D_KERNEL] ${CWARNFLAGS} ${COPTS} ${DEBUG_FLAGS}
What about renaming "DEBUG" in the kernel makefile to DEBUG_KERNEL and
use DEBUG_KERNEL instead of DEBUG_FLAGS in bsd.kmod.mk?
Bye,
Alexander.
--
Happy new year and no Y2K-crash to everyone.
http://www.Leidinger.net Alexander+Home @ Leidinger.net
Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: __sigisempty() undefined if cc -g used.
On Mon, 10 Jan 2000, Alexander Leidinger wrote: On 11 Jan, Bruce Evans wrote: Didn´t we have "makeoptions DEBUG=-g" as a kernel option to compile the kernel with debug information? What about "config -g MYKERNEL"? DEBUG is a private variable in kernel Makefiles. "config -g MYKERNEL" If I set DEBUG in make.conf it should work, right? It shouldn't work, but may. So what's private about it? It's set unconditionally in some cases. We have CFLAGS (userland) and COPTFLAGS (kernel) in make.conf, shouldn´t we also have e.g. DEBUG_FLAGS and DEBUG_KERNEL (renamed DEBUG from above)? No. Who knows what all those undocumented variables do. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
Poul-Henning Kamp wrote: Make world hangs reliably for me right now: [snip] |yacc -d -o c-parse.c c-parse.y + 0 19921 1 83 -2 0 1276 932 getblk D p00:00.09 yacc -d -o c-parse.c c-parse.y This is a softupdates filesystem on a ccd on ata... The format used for mkstemp has been changed (4 chars. longer). Does the following patch work? Index: main.c === RCS file: /home/ncvs/src/usr.bin/yacc/main.c,v retrieving revision 1.11 diff -u -r1.11 main.c --- main.c 2000/01/10 08:54:09 1.11 +++ main.c 2000/01/10 17:47:33 @@ -304,7 +304,7 @@ if (tmpdir == 0) tmpdir = "/tmp"; len = strlen(tmpdir); -i = len + 13; +i = len + 17; if (len tmpdir[len-1] != '/') ++i; -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld fails
As Pascal Hofstee wrote: With CURRENT-sources updates within an hour ago ... buildworld fails: Revert to version 1.26 of gnu/lib/libdialog/Makefile. someone broke it when he decided to install all the files in TESTS/... Don't forget to revert to 1.34 of lib/libncurses/Makefile for the same reason. Grrr. -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-pipe switch in kernel compilation
G'day, While compiling a kernel today, I noticed that the '-pipe' option to gcc was not being used. Is there any reason for this? best; gjvc -- [gjvc] 4.4BSD 4.ever! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fix for hangs with recent -current + vinum
If you're getting hangs while running vinum please update sys/dev/vinum/vinumrequest.c to version 1.41. Only people running -current compilied with version 1.40 or 1.38-1.36 of vinumrequest.c should need this fix. thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
:Make world hangs reliably for me right now: :+ :|... :|/* starting time is 16:18:8 */ :|/* ending time is 16:18:8 */ :|ln -sf gxx-hash.h hash.h :|echo '#include "cp/cp-tree.def"' gencheck.h :|echo '#include "objc/objc-tree.def"' gencheck.h :|sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" :/syv/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in c-parse.y :|yacc -d -o c-parse.c c-parse.y :+ : :0 19921 1 83 -2 0 1276 932 getblk D p00:00.09 yacc -d -o :c-parse.c c-parse.y : :This is a softupdates filesystem on a ccd on ata... : :-- :Poul-Henning Kamp FreeBSD coreteam member :[EMAIL PROTECTED] "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! No vinum? Please ps axl and pick out any other processes stuck in odd places. Then gdb -k kernel.debug /dev/mem (assuming you have kernel.debug sitting around somewhere). proc 19921 back proc ...other processes... back ... note: if you have a custom .gdbinit that sets the base to hex you may have to type the process number in hex. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
I've reproduced the softupdates ftruncate panic and have a core dump to play with. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)
In message [EMAIL PROTECTED] Jonathan Chen writes: : "Fake IRQ must be 3". Now maybe the card requires it, or maybe the : original author just didn't have anything on IRQ 3, I don't know. So, I'd : suggest turning off com2 or whatever you have on irq3, -or- change the : "fake irq" to something else you do have free on the next line (ie, : 0x3000- 0xa000 if you have IRQ10 free). If this works, great... if not, I : hope Warner gets some more free time. ;) I don't think this is the problem. The pccard interface has one interrupt pin that is mapped by the pcic bridge (or some other pccard/cardbus bridge) to the main bus of the system. I didn't change that from the 3.x driver... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
On Mon, 10 Jan 2000, Marcel Moolenaar wrote: The format used for mkstemp has been changed (4 chars. longer). Does the following patch work? Sorry, but FWIW I did test the change by recompiling cvs (which uses yacc) before I committed it :( I guess it was just the gods of stack which allowed that one to build. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: neomagic 256av/256zx audio
For what it's worth, I believe the Insperion 3500 is an oddity.
When I was dealing with OSS, the correct configuration turned out to be
a "Generic 256AV" located at 0x530, I5, DMA 01 -- that is, you treat
it just like an ordinary Windows Sound System chip (CS4231). The PCI
interface, I believe, has something to do with the funky control panel gizmo
you get in Windows that sets tone and chorus effects or some such.
I haven't looked at the driver in question, but I believe it probably expects
to use an exclusively PCI interface to the chip. Somehow, I believe the
Insperion doesn't do this.
Frank Mayhar wrote:
Cameron Grant wrote:
i have just committed a driver for the neomagic chips. please test and post
results.
Okay. I have a Dell Inspiron 3500, with a NeoMagic 256AV chipset in it.
It hangs on boot, in nm_rd() line 146. Here's the backtrace:
(kgdb) bt
#0 nm_rd (sc=0xc0d83100, regno=1536, size=2)
at ../../dev/sound/pci/neomagic.c:146
#1 0xc0206ac7 in nm_rdcd (devinfo=0xc0d83100, regno=0)
at ../../dev/sound/pci/neomagic.c:232
#2 0xc020219e in ac97_init (codec=0xc0d83000)
at ../../dev/sound/pcm/ac97.c:251
#3 0xc0202376 in ac97mix_init (m=0xc073d30c) at ../../dev/sound/pcm/ac97.c:304
#4 0xc02050b4 in mixer_init (d=0xc073d200, m=0xc0288120, devinfo=0xc0d83000)
at ../../dev/sound/pcm/mixer.c:53
#5 0xc020736b in nm_pci_attach (dev=0xc0d87280)
at ../../dev/sound/pci/neomagic.c:594
#6 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87280) at device_if.c:63
#7 0xc0148bdb in device_probe_and_attach (dev=0xc0d87280)
at ../../kern/subr_bus.c:1137
#8 0xc01498ca in bus_generic_attach (dev=0xc0d87480)
at ../../kern/subr_bus.c:1831
#9 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87480) at device_if.c:63
#10 0xc0148bdb in device_probe_and_attach (dev=0xc0d87480)
at ../../kern/subr_bus.c:1137
#11 0xc01498ca in bus_generic_attach (dev=0xc0d87b80)
at ../../kern/subr_bus.c:1831
#12 0xc01cced5 in pcib_attach (dev=0xc0d87b80) at ../../pci/pcisupport.c:747
#13 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87b80) at device_if.c:63
#14 0xc0148bdb in device_probe_and_attach (dev=0xc0d87b80)
at ../../kern/subr_bus.c:1137
#15 0xc01498ca in bus_generic_attach (dev=0xc0d87d80)
at ../../kern/subr_bus.c:1831
#16 0xc011e27e in DEVICE_ATTACH (dev=0xc0d87d80) at device_if.c:63
#17 0xc0148bdb in device_probe_and_attach (dev=0xc0d87d80)
at ../../kern/subr_bus.c:1137
#18 0xc01498ca in bus_generic_attach (dev=0xc0d86000)
at ../../kern/subr_bus.c:1831
#19 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86000) at device_if.c:63
#20 0xc0148bdb in device_probe_and_attach (dev=0xc0d86000)
at ../../kern/subr_bus.c:1137
#21 0xc01498ca in bus_generic_attach (dev=0xc0d86080)
at ../../kern/subr_bus.c:1831
#22 0xc0230c89 in nexus_attach (dev=0xc0d86080) at ../../i386/i386/nexus.c:199
#23 0xc011e27e in DEVICE_ATTACH (dev=0xc0d86080) at device_if.c:63
#24 0xc0148bdb in device_probe_and_attach (dev=0xc0d86080)
at ../../kern/subr_bus.c:1137
#25 0xc0149e0a in root_bus_configure () at ../../kern/subr_bus.c:2214
#26 0xc0227568 in configure (dummy=0x0) at ../../i386/i386/autoconf.c:146
#27 0xc013319c in mi_startup (framep=0xc0325fb4) at ../../kern/init_main.c:217
Here are the values; looks like sh has problems:
(kgdb) print /x sh
$2 = 0xc87d3000
(kgdb) print *sh
$3 = 17
(kgdb) print st
$4 = 1
(kgdb) print /x regno
$6 = 0x600
(kgdb) print *sc
$8 = {dev = 0x11, type = 0, reg = 0x0, irq = 0x0, buf = 0x0, regid = 0,
irqid = 32896, bufid = 0, ih = 0x0, ac97_base = 0, ac97_status = 0,
ac97_busy = 0, buftop = 0, pbuf = 0, rbuf = 0, cbuf = 0, acbuf = 0,
playint = 0, recint = 0, misc1int = 0, misc2int = 0, irsz = 0, badintr = 0,
pch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0, channel = 0x0,
parent = 0x0}, rch = {spd = 0, dir = 0, fmt = 0, buffer = 0x0,
channel = 0x0, parent = 0x0}}
Hmm, looks like sc-reg was never filled in.
Hope this helps.
--
Frank Mayhar [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Neomagic Sounddriver hangs HP OB4150
On Mon, 10 Jan 2000, #Michael Class wrote: The Laptop is equipped with the following Neomagic-Chip: chip1: NeoMagic MagicMedia 256AX Audio controller irq 10 at device 0.1 on pci1 The Stack-Backtrace looks exactly the same as the other mail mentioned. A little bit further digging into this shows me that on this Laptop every read access to the second memory-area of the chip in the range of 0x600-0x8ff brings the machine to a halt. I can read successfully from the areas with offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O Area starts at offset 0x600. This access brings the machine to a halt during boot. Any suggestions of what I could try? Try providing us with real data. The boot message you gave us is when pcisupport.c matches it, not when neomagic. matches it. It is impossible to recieve the above message and then have the neomagic code fall on its face. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: load spike strangeness
On Sat, 8 Jan 2000, FreeBSD wrote: list if you insist on attacking me there. Maybe Karl was right, some people in the FreeBSD organization really do think they are above the rest of us. I however do not share that belief. So, are you done? If you had half of the etiquette and knowledge on e-mail you previously have stated you have, you'd realize that phk doesn't (nor does anyone with a @FreeBSD.org) speak for the FreeBSD organization. Please crawl back into the hole you came out of. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
:I've reproduced the softupdates ftruncate panic and have a core dump :to play with. : : -Matt Ok, Kirk fixed the softupdates ftruncate panic last night. Make sure you have version 1.45 of sys/contrib/softupdates/ffs_softdep.c I would like to know if the person reporting the getblk lockup (I think it was Poul) sees that problem solved with the vinum fix that Alfred posted in regards to or whether we still have an open issue. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing...
* Matthew Dillon [EMAIL PROTECTED] [000110 12:11] wrote:
I've reproduced the softupdates ftruncate panic and have a core dump
to play with.
I don't have a panic, but rather many processes start to get stuck
in "getblk", unfortunatly they all don't stem from a common codepath,
although the first process that wedged appears to have come through
indir_trunc:
1442 d8ed2700 d93a 1001 1422 1422 004006 3 ranlib getblk cc50a85(kgdb)
proc 0xd8ed2700
(kgdb) bt
#0 mi_switch () at machine/globals.h:117
#1 0xc015d869 in tsleep (ident=0xcc50a850, priority=0x14, wmesg=0xc0292de1 "getblk",
timo=0x0)
at ../../kern/kern_synch.c:437
#2 0xc0155b06 in acquire (lkp=0xcc50a850, extflags=0x20, wanted=0x600) at
../../kern/kern_lock.c:147
#3 0xc0155dbc in lockmgr (lkp=0xcc50a850, flags=0x10022, interlkp=0xc030ba74,
p=0xd8ed2700)
at ../../kern/kern_lock.c:362
#4 0xc017e73e in getblk (vp=0xd66dab20, blkno=0xe565a0, size=0x2000, slpflag=0x0,
slptimeo=0x0) at ../../sys/buf.h:294
#5 0xc017c72a in bread (vp=0xd66dab20, blkno=0xe565a0, size=0x2000, cred=0x0,
bpp=0xd93a1bb8)
at ../../kern/vfs_bio.c:498
#6 0xc02015af in indir_trunc (ip=0xd93a1bfc, dbn=0xe565a0, level=0x0, lbn=0xc,
countp=0xd93a1bec)
at ../../ufs/ffs/ffs_softdep.c:2040
#7 0xc02013f5 in handle_workitem_freeblocks (freeblks=0xc2315300) at
../../ufs/ffs/ffs_softdep.c:1961
#8 0xc0200e40 in softdep_setup_freeblocks (ip=0xc23ca200, length=0x0) at
../../ufs/ffs/ffs_softdep.c:1668
#9 0xc01fead6 in ffs_truncate (vp=0xd9072860, length=0x0, flags=0x0, cred=0x0,
p=0xd8ed2700)
at ../../ufs/ffs/ffs_inode.c:195
#10 0xc0209276 in ufs_inactive (ap=0xd93a1eb8) at ../../ufs/ufs/ufs_inode.c:84
#11 0xc020e3bd in ufs_vnoperate (ap=0xd93a1eb8) at ../../ufs/ufs/ufs_vnops.c:2283
#12 0xc0185145 in vput (vp=0xd9072860) at vnode_if.h:794
#13 0xc0188739 in unlink (p=0xd8ed2700, uap=0xd93a1f80) at
../../kern/vfs_syscalls.c:1421
#14 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi =
0x808b300, tf_esi = 0x8076170,
tf_ebp = 0xbfbffa04, tf_isp = 0xd93a1fd4, tf_ebx = 0x8076160, tf_edx =
0x8074060, tf_ecx = 0x0, tf_eax = 0xa,
tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x180c41cc, tf_cs = 0x1f, tf_eflags =
0x293, tf_esp = 0xbfbff9c8,
tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057
after that it starts spreading:
1478 d8ed3480 d8f32000 1001 1477 1478 004006 3 zsh getblk cc50b148
1477 d8ed3a80 d8f24000 1001 369 1477 004106 3 rxvt getblk cc50b148
1473 d8ed2a00 d8fbf000 1001 1466 1473 004006 3 cvs getblk cc4a39e8
with varied tracebacks:
(kgdb) proc 0xd8ed3480
(kgdb) bt
#0 mi_switch () at machine/globals.h:117
#1 0xc015d869 in tsleep (ident=0xcc50b148, priority=0x14, wmesg=0xc0292de1 "getblk",
timo=0x0)
at ../../kern/kern_synch.c:437
#2 0xc0155b06 in acquire (lkp=0xcc50b148, extflags=0x20, wanted=0x600) at
../../kern/kern_lock.c:147
#3 0xc0155dbc in lockmgr (lkp=0xcc50b148, flags=0x10022, interlkp=0xc030ba74,
p=0xd8ed3480)
at ../../kern/kern_lock.c:362
#4 0xc017e73e in getblk (vp=0xd66dcf60, blkno=0x20090, size=0x2000, slpflag=0x0,
slptimeo=0x0) at ../../sys/buf.h:294
#5 0xc017c72a in bread (vp=0xd66dcf60, blkno=0x20090, size=0x2000, cred=0x0,
bpp=0xd8f33dec)
at ../../kern/vfs_bio.c:498
#6 0xc01fe869 in ffs_update (vp=0xd8e880e0, waitfor=0x0) at
../../ufs/ffs/ffs_inode.c:98
#7 0xc02092ca in ufs_inactive (ap=0xd8f33e40) at ../../ufs/ufs/ufs_inode.c:92
#8 0xc020e3bd in ufs_vnoperate (ap=0xd8f33e40) at ../../ufs/ufs/ufs_vnops.c:2283
#9 0xc018507d in vrele (vp=0xd8e880e0) at vnode_if.h:794
#10 0xc018bbb3 in vn_close (vp=0xd8e880e0, flags=0x1, cred=0xc2243c80, p=0xd8ed3480)
at ../../kern/vfs_vnops.c:232
#11 0xc018c414 in vn_closefile (fp=0xc1fb6000, p=0xd8ed3480) at
../../kern/vfs_vnops.c:630
#12 0xc01526fd in fdrop (fp=0xc1fb6000, p=0xd8ed3480) at ../../sys/file.h:211
#13 0xc015263b in closef (fp=0xc1fb6000, p=0xd8ed3480) at
../../kern/kern_descrip.c:1003
#14 0xc0151d98 in close (p=0xd8ed3480, uap=0xd8f33f80) at ../../kern/kern_descrip.c:507
#15 0xc026f7ba in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi =
0x80a9000, tf_esi = 0x1,
tf_ebp = 0xbfbff9c8, tf_isp = 0xd8f33fd4, tf_ebx = 0x1816d3c4, tf_edx =
0x80a9138, tf_ecx = 0x2, tf_eax = 0x6,
tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x1812a22c, tf_cs = 0x1f, tf_eflags =
0x283, tf_esp = 0xbfbff98c,
tf_ss = 0x2f}) at ../../i386/i386/trap.c:1057
(kgdb) proc 0xd8ed3a80
(kgdb) bt
#0 mi_switch () at machine/globals.h:117
#1 0xc015d869 in tsleep (ident=0xcc50b148, priority=0x14, wmesg=0xc0292de1 "getblk",
timo=0x0)
at ../../kern/kern_synch.c:437
#2 0xc0155b06 in acquire (lkp=0xcc50b148, extflags=0x20, wanted=0x600) at
../../kern/kern_lock.c:147
#3 0xc0155dbc in lockmgr (lkp=0xcc50b148, flags=0x10022, interlkp=0xc030ba74,
p=0xd8ed3a80)
at ../../kern/kern_lock.c:362
#4 0xc017e73e in getblk (vp=0xd66dcf60, blkno=0x20090,
Re: freezing... update to 1.45 of ffs_softdep.c
* Matthew Dillon [EMAIL PROTECTED] [000110 14:09] wrote: :I've reproduced the softupdates ftruncate panic and have a core dump :to play with. : : -Matt Ok, Kirk fixed the softupdates ftruncate panic last night. Make sure you have version 1.45 of sys/contrib/softupdates/ffs_softdep.c I would like to know if the person reporting the getblk lockup (I think it was Poul) sees that problem solved with the vinum fix that Alfred posted in regards to or whether we still have an open issue. still a problem, just got snagged a few moments ago, there's a traceback already on the way. :) -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
In message [EMAIL PROTECTED], Matthew Dillon writes: I would like to know if the person reporting the getblk lockup (I think it was Poul) sees that problem solved with the vinum fix that Alfred posted in regards to or whether we still have an open issue. I don't use vinum and -current as cvsup'ed right now has the problem. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
: I would like to know if the person reporting the getblk lockup (I think : it was Poul) sees that problem solved with the vinum fix that Alfred : posted in regards to or whether we still have an open issue. : :still a problem, just got snagged a few moments ago, there's a traceback :already on the way. :) : :-Alfred Is this backed by the ata driver too? If so, if either you or Poul could backoff to the wd driver and see if the problem continues, I would appreciate it. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
::still a problem, just got snagged a few moments ago, there's a traceback ::already on the way. :) :: ::-Alfred : :Is this backed by the ata driver too? : :If so, if either you or Poul could backoff to the wd driver and see :if the problem continues, I would appreciate it. I was able to reproduce it. Never mind re: trying to use the 'wd' driver. It occurs for me w/ SCSI. It looks like a softupdates problem for sure. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: neomagic 256av/256zx audio
Frank Mayhar wrote: Well, this doesn't help me a whole lot with pcm. I think it does. Try configuring pcm0 at 0x534 (4, not 0), irq 5, dma 0, flags 0x11 (presuming the BIOS says 0x530, irq 5, dma 0 1). This did work for me once upon a time, modulo bugs in the old pcm code. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: mouse problem(please help)
On 10-Jan-00 Satyajit Das wrote: mouse not working . Again i run XF86Setup program ,I also choose system , sysmouse" and port /dev/cuaa1 or /dev/sysmouse but no work. please help me how can i work mouse in Xwindows. Well, if the mouse works on the console, then moused is working OK. You should double check your X configuration.. The port should be /dev/sysmouse, and the protocol MouseSystems. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
* Matthew Dillon [EMAIL PROTECTED] [000110 15:13] wrote: ::still a problem, just got snagged a few moments ago, there's a traceback ::already on the way. :) :: ::-Alfred : :Is this backed by the ata driver too? : :If so, if either you or Poul could backoff to the wd driver and see :if the problem continues, I would appreciate it. I was able to reproduce it. Never mind re: trying to use the 'wd' driver. It occurs for me w/ SCSI. It looks like a softupdates problem for sure. ugh, what fun this is, yes, i'm using vinum, softupdates, nfs and ata, but da for the vinum backing. I think i'm one of the bio bug posterboys. Anyhow, it seems that the problem happens because somewhere softupdates (or something else perhaps) LK_KERNPROCs the buffer and never lets go. I've been trying to compile with DEBUG_LOCKS for nearly half an hour but i'm having difficulty with vinum because i think it's intent on giving me a hard time w/ matching itself and the kernel and the userland. argh.. :) -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange SCSI related system hang
In article [EMAIL PROTECTED] you wrote: Hi all, This morning I had a very strange (at least I've never seen it before) SCSI related system hang. The system simply stopped responding at 9:30:03 am this morning. I found it in this state at 13:20. It had been hanging _hard_. No response to console, serial terminal or network. After a hard reset the system came back online normally and is working normally again. Note that the machine had an uptime of 4 days, 14 hours before the problem occured and it never happened before. Could this be a hardware problem? Perhaps. Is your WD drive getting hot? The ahc driver believes that, during a message out phase, the target simply dropped off the bus. It may be that the ahc driver did something to provoke that, but without a bus analyzer on the drive, it is hard to know. According to the progrom counter, we are waiting for the target to request the next byte at the time this occurs, but that request never comes. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pppctl/ppp bug
Hi, I've noticed that pppctl hangs 100% repeatable when I'm doing "set log local +chat" followed by the "dial" command over diagnostic socket. In the case when the "dial" command being sent over other socket this behaviour doesn't observed. Following I'm attaching transcript of my sessions -Maxim Hi, Does it still hang if you also enable debug logging ? And if so, what sort of output to you see ? It's possible (perhaps) that the socket is blocking. If you open a connection that hangs then open a second connection, do you get the second one ok ? If so, what does ``show who'' and ``show route'' come up with - on both diagnostic connections ? Cheers. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: When does the 4.x branch go stable?
In message v04220815b49f8c375699@[195.238.1.121], Brad Knowles writes: At 11:46 PM +1100 2000/1/10, Jonathan Michaels wrote: what sort of hardware problems, please ? Issues with some older Pentium motherboards apparently losing their minds (and their timing interrupts) with the new ATA driver (replaces the old wd driver). There are also some issues with laptops and PC Cards, especially CardBus cards. I currently have a couple of older machines, a P120 and a 486DX/33 happily running 3.4. Would you recommend installing 4.0-current on a spare slice to verify whether it will run on these older machines or should I wait until -current settles down, e.g. is more or less in a bug-fix state? Any other pitfalls one would need to consider prior to running this kind of test? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED] ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RAID benchmarks (was: Adaptec AAC-364 RAID controllersupport)
At 4:47 PM +0800 2000/1/9, Greg Lehey wrote: I've updated rawio and the port, and if you (anybody) are really interested in sequential performance, you should run the tests again. Unfortunately, that machine is no longer available for benchmarking. However, I might have another benchmarking opportunity in the near future with our replacement news spool server, so we'll have to see what I can do in the short amount of time I will have available to me. -- These are my opinions -- not to be taken as official Skynet policy |o| Brad Knowles, [EMAIL PROTECTED]Belgacom Skynet NV/SA |o| |o| Systems Architect, News FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
The following patch should fix the problem temporarily until
Kirk can dig into it and figure out what went wrong.
-Matt
Index: sys/contrib//softupdates/ffs_softdep.c
===
RCS file: /FreeBSD/FreeBSD-CVS/src/sys/contrib/softupdates/ffs_softdep.c,v
retrieving revision 1.45
diff -u -r1.45 ffs_softdep.c
--- sys/contrib//softupdates/ffs_softdep.c 2000/01/10 08:39:03 1.45
+++ sys/contrib//softupdates/ffs_softdep.c 2000/01/11 00:20:55
@@ -1663,10 +1663,13 @@
* still have a bitmap dependency, then the inode has never been
* written to disk, so we can process the freeblks immediately.
*/
+#if 0
if ((inodedep-id_state DEPCOMPLETE) == 0) {
FREE_LOCK(lk);
handle_workitem_freeblocks(freeblks);
- } else {
+ } else
+#endif
+ {
WORKLIST_INSERT(inodedep-id_bufwait, freeblks-fb_list);
FREE_LOCK(lk);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
i want to join the mailing list.!
how do i.? :) --MIME Multi-part separator-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: freezing... update to 1.45 of ffs_softdep.c
In article [EMAIL PROTECTED] you wrote: In message [EMAIL PROTECTED], Matthew Dillon writes: I would like to know if the person reporting the getblk lockup (I think it was Poul) sees that problem solved with the vinum fix that Alfred posted in regards to or whether we still have an open issue. I don't use vinum and -current as cvsup'ed right now has the problem. I just saw the same: two processes got frozen in getblk (tin and mutt). No makeworld, no activity on the system at all -- just reading news and mail. After a minute or so the whole system froze. It's with version 1.46 of ffs_softdep.c -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! --- "Nuclear war can ruin your whole compile." -- Karl Lehenbauer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i want to join the mailing list.!
On Tue, 11 Jan 2000, °í¹ü¼® wrote: how do i.? :) http://www.freebsd.org/support.html#mailing-list Chuck Robey| Interests include C Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATAPI broken, but why?
I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the ATA driver, at least, being broken (WRT CD-Rs). The question is, does anyone have any idea at all why? I tried reverting to just before the CDRIOC* changes, and that didn't help (using wormcontrol to test that). If any of you have any hints at all, please let me know. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI broken, but why?
On Mon, 10 Jan 2000, Brian Fundakowski Feldman wrote: I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the ATA driver, at least, being broken (WRT CD-Rs). The question is, does anyone have any idea at all why? I tried reverting to just before the CDRIOC* changes, and that didn't help (using wormcontrol to test that). If any of you have any hints at all, please let me know. I just wanted to add for all to see that prior to the CDRIOC* changes, all was OK with my HP 8250i CD-RW unit, reading and writing both worked fine. After the changes, writing no longer works. All I get is WRITE_BIG errors from burncd (the write light never turns on) then the driver endlessly tries to reset the CD-R drive and I have to hit the reset button to reboot. My HP Colorado 8G ATAPI tape never probed/worked at all with the new ATA driver. Anyone out there have one that's working? The wd* drivers, although obselete now, handled all of my ATA-ATAPI stuff without any problems. I find it hard to believe that 4.0 will get released with less hardware support than 3.x. -Bryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: neomagic 256av/256zx audio
Cameron Grant wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] I did that and it still hangs. Let me see if it's for the same reason. Maybe *sc is getting stepped on somehow? very odd. i have no idea what is going on. i have committed bits, so try again in a few hours. Okay, I've rebuilt the kernel and rerun the test, again doing remote debugging. As I thought, the zeroed *sc was a quirk of that debugging session. The same hang is happening to me as is happening to the other guy with a hang at 0x600 (sorry, I forgot his name and didn't retain the email). Here's the backtrace: #0 nm_rd (sc=0xc0d83100, regno=1536, size=2) at ../../dev/sound/pci/neomagic.c:142 #1 0xc0207267 in nm_rdcd (devinfo=0xc0d83100, regno=0) at ../../dev/sound/pci/neomagic.c:232 #2 0xc020293e in ac97_init (codec=0xc0d83000) at ../../dev/sound/pcm/ac97.c:251 #3 0xc0202b16 in ac97mix_init (m=0xc073d30c) at ../../dev/sound/pcm/ac97.c:304 #4 0xc0205854 in mixer_init (d=0xc073d200, m=0xc0288c40, devinfo=0xc0d83000) at ../../dev/sound/pcm/mixer.c:53 #5 0xc0207b4b in nm_pci_attach (dev=0xc0d87280) at ../../dev/sound/pci/neomagic.c:595 #6 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87280) at device_if.c:63 #7 0xc0148b87 in device_probe_and_attach (dev=0xc0d87280) at ../../kern/subr_bus.c:1137 #8 0xc0149876 in bus_generic_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1831 #9 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87480) at device_if.c:63 #10 0xc0148b87 in device_probe_and_attach (dev=0xc0d87480) at ../../kern/subr_bus.c:1137 #11 0xc0149876 in bus_generic_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1831 #12 0xc01cd235 in pcib_attach (dev=0xc0d87b80) at ../../pci/pcisupport.c:747 #13 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87b80) at device_if.c:63 #14 0xc0148b87 in device_probe_and_attach (dev=0xc0d87b80) at ../../kern/subr_bus.c:1137 #15 0xc0149876 in bus_generic_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1831 #16 0xc011e1be in DEVICE_ATTACH (dev=0xc0d87d80) at device_if.c:63 #17 0xc0148b87 in device_probe_and_attach (dev=0xc0d87d80) at ../../kern/subr_bus.c:1137 #18 0xc0149876 in bus_generic_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1831 #19 0xc011e1be in DEVICE_ATTACH (dev=0xc0d86000) at device_if.c:63 #20 0xc0148b87 in device_probe_and_attach (dev=0xc0d86000) at ../../kern/subr_bus.c:1137 #21 0xc0149876 in bus_generic_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1831 #22 0xc0231579 in nexus_attach (dev=0xc0d86080) at ../../i386/i386/nexus.c:199 #23 0xc011e1be in DEVICE_ATTACH (dev=0xc0d86080) at device_if.c:63 #24 0xc0148b87 in device_probe_and_attach (dev=0xc0d86080) at ../../kern/subr_bus.c:1137 #25 0xc0149db6 in root_bus_configure () at ../../kern/subr_bus.c:2214 #26 0xc0227e58 in configure (dummy=0x0) at ../../i386/i386/autoconf.c:146 #27 0xc0133118 in mi_startup (framep=0xc0326fb4) at ../../kern/init_main.c:217 (kgdb) print /x regno $1 = 0x600 The hang is happening on the "movzwl (%ebx,%eax,1),%eax" at nm_rd+80: (kgdb) s 146 return bus_space_read_2(st, sh, regno); (kgdb) print $eip $2 = (void *) 0xc0207054 (kgdb) stepi 0xc0207056 146 return bus_space_read_2(st, sh, regno); (kgdb) stepi 198 #if defined(_I386_BUS_MEMIO_H_) (kgdb) print $eip $3 = (void *) 0xc0207060 That's this instruction: 0xc0207060 nm_rd+80: movzwl (%ebx,%eax,1),%eax (kgdb) print /x $ebx $5 = 0x600 (kgdb) print /x $eax $6 = 0xc87d2000 $eax being 0xc87d2000 seems a little odd, but I don't remember my 80x86 assembly well enough to say whether it's right or wrong. In the meantime, I'll try Nick Sayer's trick. -- Frank Mayhar [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -pipe switch in kernel compilation
On Mon, Jan 10, 2000 at 04:55:43PM +, George Cox wrote: G'day, While compiling a kernel today, I noticed that the '-pipe' option to gcc was not being used. Is there any reason for this? I think this is the (historical) default, so that people with only 4-8 MB of RAM don't get into trouble ;-) Where 4 MB isn't sufficient anymore with a GENERIC kernel. You need at least 6 MB or so to boot, then compile a custom kernel and then, if you are lucky, can perhaps run with 4 MB. But that information is about 1-2 years old, don't know, if we perhaps already need 6-8 MB nowadays... Though it's zillions better than M$ crap. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ssh2: piperd = hanging?
Trying to use cvs to get a working copy of /usr/src from the /home/ncvs of one machine to another, cvs just hangs. Top displays as state for cvs `piperd'. I have not been able to find this documented in the top man page. A guess: pipe reading data? In my case it indicates cvs or ssh hanging :-( There are no data read anymore in any case (for which top seems to print `getblk' or `RUN' during the short time cvs works). Things remain like this until I kill cvs through ^C. This happens a few seconds after entering the cvs command. When I retry: the same result, but not always at the same file. Maybe I should mention that after entering the password (for ssh) I get: `stdin isn't a terminal'. The solution for this problem seems to be to set CVS_RSH to ssh1. Both `ssh' and `ssh2' produce the abortive cvs. Both machines run ssh2 2.0.13 from the ports. uname -a: ... 4.0 CURRENT Dec 26 ... 1999 -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] propro7:00am up 11 days, 8:49, load average: 2.03 2.04 2.00 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ssh2: piperd = hanging?
Marc Schneiders wrote: Trying to use cvs to get a working copy of /usr/src from the /home/ncvs of one machine to another, cvs just hangs. Top displays as state for cvs `piperd'. I have not been able to find this documented in the top man page. A guess: pipe reading data? In my case it indicates cvs or ssh hanging :-( There are no data read anymore in any case (for which top seems to print `getblk' or `RUN' during the short time cvs works). Things remain like this until I kill cvs through ^C. `piperd' means a process is reading from a pipe. In your case, maybe reading from a pipe is causing a hang. Of course, the inverse of piperd is pipewt, I believe, which means the process is writing to a pipe. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: load spike strangeness
Since when does an E-mail address require a "realname"? Only a imbecile (IMHO) would use their real name on an e-mail that goes out to a public list. I don't want people to know my real name or SSN or any other personal info for that matter, NOR is it required, as far as I know. If it were to become required, I'd prefer to "unsubscribe" than to give that info out, as would any other intelligent person. I suggest you check your e-mail security information again before babbling nonsense. My e-mail addy is a REAL addy not one that goes through an anonymous re-mailer and I use it so IF I start getting Spam I can easily rmuser it and create another to resubscribe. Do you also use you real full name on IRC? To quote "Mr. T": "I pity da f00!" I think he was talking about the text that accompanies your e-mail address. E.g. Bill Gates billy@micro$.com and Bill Gates william@micro$.com is the same user for human processing, but 2 completely different people when it comes to spam. Sometimes I long for the days when people on The Internet were just a few and netiquette ruled the day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
