Re: CURRENT is freezing again ...
It seems Michael C . Wu wrote: > I had those problems too a while ago on a UP p3-650 laptop. Finally I just > newfs'ed the machine and installed the 20001028 snapshot, then cvsupp'ed > to 20001122. The laptop now works well. What I saw was processes > forking and forking again until the machine runs out of memory and > swap. I think it may be some old libraries left over from > upgrades and make world. Hmm, this is a new installed box, so there is no old leftovers... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /tmp
On Thu, Nov 16, 2000 at 03:18:09PM +, void <[EMAIL PROTECTED]> wrote: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. Is there a supported way to locally override BSD.var.dist, or > do I need to install mutt setgid mail, or what? Be sure that mutt_dotlock is setgid mail and is a member of group mail. Just got the same thing yesterday while trying out CVS version of Mutt. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote: > I would try a new kernel, and perhaps some collabaration with John > to debug these problems rather than just complaining about the > situation. I see at least two experianced developers in the CC > list, there's no reason for these poor bug reports. The problem with a hard lock-up out of which you can't escape into the debugger is that it makes meaningful bug reports impossible. My non-SMP workstation has exhibited apparently arbitrary lock-ups since the advent of SMPng. I thought I was the only one, since my question on the freebsd-current mailing list went unanswered. >From my understanding, John's WITNESS code allows us to break into the debugger from within interrupt context. If the lock-ups are happening in there, then this may help us provide better bug reports. Oh, and a couple of deep breaths are probably in order. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /tmp
On Thu, 16 Nov 2000 15:18:09 GMT, void wrote: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. Is there a supported way to locally override BSD.var.dist, or > do I need to install mutt setgid mail, or what? You get two answers here. 1) 1777 on /var/mail is bad, bad, bad. Don't do that. 2) The easiest way to override the permissions and ownerships enforced during a make world is to use CVS to update your sources so that your local hacks to src/etc/mtree/BSD.*.dist are not overwritten on update. There are other ways, but the bottom line is that you should find a way to ensure that those files are modified to your taste before every world update. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
It seems Sheldon Hearn wrote: > > I would try a new kernel, and perhaps some collabaration with John > > to debug these problems rather than just complaining about the > > situation. I see at least two experianced developers in the CC > > list, there's no reason for these poor bug reports. > > The problem with a hard lock-up out of which you can't escape into the > debugger is that it makes meaningful bug reports impossible. My non-SMP > workstation has exhibited apparently arbitrary lock-ups since the advent > of SMPng. > > I thought I was the only one, since my question on the freebsd-current > mailing list went unanswered. You are _not_ alone, there has been numerous complains about this on the list, but so far they have not been taken seriously :| > >From my understanding, John's WITNESS code allows us to break into the > debugger from within interrupt context. If the lock-ups are happening > in there, then this may help us provide better bug reports. It doesn't help here at least, the machine(s) just lock up solid only reset or a powercycle can bring them back... > Oh, and a couple of deep breaths are probably in order. :-) Yeah like *sigh* -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /tmp
On Fri, Nov 17, 2000 at 01:52:27PM +0200, Sheldon Hearn <[EMAIL PROTECTED]> wrote: > > I have a similar problem -- every time I make world, perms on /var/mail > > get set to 775. Mutt considers my mailbox read-only until I change it > > to 1777. Is there a supported way to locally override BSD.var.dist, or > > do I need to install mutt setgid mail, or what? > > You get two answers here. [snip] Don't install mutt setgid mail, the mutt_dotlock external program is supposed to be setgid mail. This is what it looks like in my system: 8 -rwxr-xr-x 1 vallo wheel6740 Nov 16 10:48 flea* 480 -rwxr-xr-x 1 vallo wheel 460808 Nov 16 10:49 mutt* 8 -rwxr-sr-x 1 vallo mail 7288 Nov 16 10:49 mutt_dotlock* 2 -rwxr-xr-x 1 vallo wheel 26 Nov 16 10:48 muttbug* 2 -rwxr-xr-x 1 vallo wheel 274 Nov 16 10:48 pgpewrap* 24 -rwxr-xr-x 1 vallo wheel 22700 Nov 16 10:49 pgpring* -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Fri, 17 Nov 2000 12:55:28 +0100 (CET), Soren Schmidt <[EMAIL PROTECTED]> said: > It doesn't help here at least, the machine(s) just lock up solid > only reset or a powercycle can bring them back... Same here ... as others noted, started with SMPng ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] There are things that are so serious that you can only joke about them. -- Werner Heisenberg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first moduledirectory twice]
obrien> [its easier to read patches when they aren't quoted in their entirety ;-)]
Attached below is a patch which I've made before. If nothing is going
wrong, please commit this change current.jp.FreeBSD.org which
employs 'make -j' option have missed -current release since the
beginning of this month.
-- -
Makoto `MAR' MATSUSHITA
Index: Makefile
===
RCS file: /lab/FreeBSD/FreeBSD.cvs/src/release/Makefile,v
retrieving revision 1.585
diff -c -r1.585 Makefile
*** Makefile2000/11/12 11:04:11 1.585
--- Makefile2000/11/13 05:37:12
***
*** 831,837
@rm -f ${RD}/kernels/*.ko
@cd ${.CURDIR}/../sys/${MACHINE}/conf && config ${KERNEL}
@cd ${.CURDIR}/../sys/compile/${KERNEL} && \
! make kernel-depend && \
make ${KERNEL_FLAGS} modules && \
make modules-reinstall DESTDIR=${RD}/kernels && \
--- 831,837
@rm -f ${RD}/kernels/*.ko
@cd ${.CURDIR}/../sys/${MACHINE}/conf && config ${KERNEL}
@cd ${.CURDIR}/../sys/compile/${KERNEL} && \
! make modules-depend && \
make ${KERNEL_FLAGS} modules && \
make modules-reinstall DESTDIR=${RD}/kernels && \
Index: Makefile.alpha
===
RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.alpha,v
retrieving revision 1.79
diff -c -r1.79 Makefile.alpha
*** Makefile.alpha 2000/10/29 09:47:50 1.79
--- Makefile.alpha 2000/11/14 01:55:17
***
*** 252,258
echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \
sort -u | comm -23 - dontlink | \
sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks
! sh makelinks && rm -f dontlink
kernel-tags:
@[ -f .depend ] || { echo "you must make depend first"; exit 1; }
--- 252,258
echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \
sort -u | comm -23 - dontlink | \
sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks
! sh makelinks; rm -f dontlink
kernel-tags:
@[ -f .depend ] || { echo "you must make depend first"; exit 1; }
***
*** 309,338
MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR}
modules:
! @mkdir -p ${.OBJDIR}/modules
! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj all
modules-depend:
@mkdir -p ${.OBJDIR}/modules
! cd $S/modules && env ${MKMODULESENV} ${MAKE} obj depend
modules-clean:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} clean
modules-cleandepend:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandepend
modules-cleandir:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} cleandir
modules-tags:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} tags
modules-install modules-install.debug:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} install
modules-reinstall modules-reinstall.debug:
! cd $S/modules && env ${MKMODULESENV} ${MAKE} install
config.o:
${NORMAL_C}
--- 309,342
MKMODULESENV= MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${KODIR}
modules:
! @if [ ! -d ${.OBJDIR}/modules ]; then \
! echo You must run make depend before building modules; \
! exit 1; \
! fi
! cd $S/modules; env ${MKMODULESENV} ${MAKE} all
modules-depend:
@mkdir -p ${.OBJDIR}/modules
! cd $S/modules; env ${MKMODULESENV} ${MAKE} obj; \
! env ${MKMODULESENV} ${MAKE} depend
modules-clean:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} clean
modules-cleandepend:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandepend
modules-cleandir:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} cleandir
modules-tags:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} tags
modules-install modules-install.debug:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} install
modules-reinstall modules-reinstall.debug:
! cd $S/modules; env ${MKMODULESENV} ${MAKE} install
config.o:
${NORMAL_C}
Index: Makefile.i386
===
RCS file: /lab/FreeBSD/FreeBSD.cvs/src/sys/conf/Makefile.i386,v
retrieving revision 1.212
diff -c -r1.212 Makefile.i386
*** Makefile.i386 2000/10/29 09:47:50 1.212
--- Makefile.i386 2000/11/14 01:55:15
***
*** 212,218
echo ${CFILES} | tr -s ' ' '\12' | sed 's/\.c/.o/' | \
sort -u | comm -23 - dontlink | \
sed 's,../.*/\(.*.o\),rm -f \1;ln -s ../GENERIC/\1 \1,' > makelinks
! sh makelinks && rm -f dontlink
kernel-tags:
@[ -f .depend ] || { echo "you must make depend first"; exit 1; }
--- 212,218
echo ${CFILES} | tr -s ' ' '\12'
Unsubscribed from AfroConnection2
Dear , You have just been removed from the following EmailFactory Mailing Lists: 1.- AfroConnection2 Thank You. Sincerely, EmailFactory.com staff. This email sent by http://www.EmailFactory.com The Web-Based Precision Opt-In Email Marketing Solution. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
heads up: sizeof proc changed
As usual, you'll have to recompile all libkvm using programs. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
In message <[EMAIL PROTECTED]> Sheldon Hearn writes: : The problem with a hard lock-up out of which you can't escape into the : debugger is that it makes meaningful bug reports impossible. My non-SMP : workstation has exhibited apparently arbitrary lock-ups since the advent : of SMPng. You can also short IOCHK to ground to get an NMI which kicks you into the debugger, even in an interrupt context. I have a card I built from an old multi-function card to do this. I think it is A1 and A2, but I don't have my ISA bus spec handy. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On 17-Nov-00 Sheldon Hearn wrote: > > > On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote: > >> I would try a new kernel, and perhaps some collabaration with John >> to debug these problems rather than just complaining about the >> situation. I see at least two experianced developers in the CC >> list, there's no reason for these poor bug reports. > > The problem with a hard lock-up out of which you can't escape into the > debugger is that it makes meaningful bug reports impossible. My non-SMP > workstation has exhibited apparently arbitrary lock-ups since the advent > of SMPng. When I get a hard lock like this I usually try to see if I can reproduce it in single user mode. If I can, then I compile KTR into my kernel with the following options: KTR, KTR_EXTEND, KTR_COMPILE="0x3fff", KTR_MASK="(KTR_INTR|KTR_PROC)". Then I boot into single user (so I don't dirty filesystems), mount any needed fs's as read only if possible, and run the following command: # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom And then stare at the tracing output on teh screen to see what the machine was doing when it hung. I.e., to see if it is still getting interrupts, and to see what process it died in, etc. > From my understanding, John's WITNESS code allows us to break into the > debugger from within interrupt context. If the lock-ups are happening > in there, then this may help us provide better bug reports. Err, not quite. It's BSD/OS's WITNESS code, and what the WITNESS code does is perform extra checks on mutex enter's and exit's to ensure that we aren't handling mutexes in such a way that a deadlock is possible. Thus, it verifies that you don't grab mutexes out of order, or that you don't grab sleep mutexes with interrupts disabled, etc. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
In message <[EMAIL PROTECTED]>, Warner Losh writes: >In message <[EMAIL PROTECTED]> Sheldon Hearn writes: >: The problem with a hard lock-up out of which you can't escape into the >: debugger is that it makes meaningful bug reports impossible. My non-SMP >: workstation has exhibited apparently arbitrary lock-ups since the advent >: of SMPng. > >You can also short IOCHK to ground to get an NMI which kicks you into >the debugger, even in an interrupt context. Bad news for you warner: On a too large sample of my newer motherboards this doesn't work anymore :-( -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
In message <25636.974487067@critter> Poul-Henning Kamp writes: : In message <[EMAIL PROTECTED]>, Warner Losh writes: : >In message <[EMAIL PROTECTED]> Sheldon Hearn writes: : >: The problem with a hard lock-up out of which you can't escape into the : >: debugger is that it makes meaningful bug reports impossible. My non-SMP : >: workstation has exhibited apparently arbitrary lock-ups since the advent : >: of SMPng. : > : >You can also short IOCHK to ground to get an NMI which kicks you into : >the debugger, even in an interrupt context. : : Bad news for you warner: On a too large sample of my newer : motherboards this doesn't work anymore :-( There's also a pci signal that you can either pull up or pull down that's supposed to give you the same results. I've never really needed to know it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Fri, Nov 17, 2000 at 11:26:02AM -0700, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Sheldon Hearn writes: > : The problem with a hard lock-up out of which you can't escape into the > : debugger is that it makes meaningful bug reports impossible. My non-SMP > : workstation has exhibited apparently arbitrary lock-ups since the advent > : of SMPng. > > You can also short IOCHK to ground to get an NMI which kicks you into > the debugger, even in an interrupt context. I have a card I built > from an old multi-function card to do this. I think it is A1 and A2, > but I don't have my ISA bus spec handy. Just stick a metal pin (ballpoint works well) into the ISA connector between the pins closest to the back of the machine. That is IOCHKN and GND respectively. Wilko [hardware designer gone bad..] -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module directory twice]
On Fri, Nov 17, 2000 at 10:55:32PM +0900, Makoto MATSUSHITA wrote: > Attached below is a patch which I've made before. If nothing is going > wrong, please commit this change I committed something simular. BTW, you made ``make depend'' a requirement, which we did not have agreement on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom All very well and good once you've figured out which command makes your machine go boom. But as I said, the locks I'm getting appear completely arbitrary. I'm no hard-core hacker, but I'm not completely clueless when it comes to isolating problems by way of deductive reasoning, and I'm stumped as to what's causing these. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module d
On 17-Nov-00 David O'Brien wrote: > On Fri, Nov 17, 2000 at 10:55:32PM +0900, Makoto MATSUSHITA wrote: >> Attached below is a patch which I've made before. If nothing is going >> wrong, please commit this change > > I committed something simular. BTW, you made ``make depend'' a > requirement, which we did not have agreement on. Erm: > config -g LAPTOP Don't forget to do a ``make depend'' Kernel build directory is ../../compile/LAPTOP make depend is already a requirement. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On 17-Nov-00 Sheldon Hearn wrote: > > > On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > >> # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom > > All very well and good once you've figured out which command makes your > machine go boom. Yes, I know. I didn't say the method was perfect. I find it frustrating as well. :-/ > But as I said, the locks I'm getting appear completely arbitrary. I'm > no hard-core hacker, but I'm not completely clueless when it comes to > isolating problems by way of deductive reasoning, and I'm stumped as to > what's causing these. I have no idea either. :( I can't magically fix them, and if I don't commit any of this stuff which works on my boxes as far as I can tell, then others won't test it and we won't make progress. If a buildworld usually triggers, then try writing a small C program that beats on a file in /tmp or /var, then start up 10 copies of it in a script that you run as your 'command_that_makes_my_machine_go_boom' to see if it works. :-P > Ciao, > Sheldon. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RQ review: [was: Re: "make modules" kicks the first module d
On Fri, Nov 17, 2000 at 02:06:44PM -0800, John Baldwin wrote: > > I committed something simular. BTW, you made ``make depend'' a > > requirement, which we did not have agreement on. > > Erm: > > config -g LAPTOP > Don't forget to do a ``make depend'' > Kernel build directory is ../../compile/LAPTOP > > make depend is already a requirement. "Erm", that is a recommendation. It is not a requirement. The posted patch made it so you were forced to. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unsubscribed from AfroConnection2
Dear , You have just been removed from the following EmailFactory Mailing Lists: 1.- AfroConnection2 Thank You. Sincerely, EmailFactory.com staff. This email sent by http://www.EmailFactory.com The Web-Based Precision Opt-In Email Marketing Solution. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kern/22838: if_tap and linprocfs modules are brokern in -current
[EMAIL PROTECTED] writes: > when i try to kldload if_tap module, the kernel says "symbol lminor > undefined" and fails to load the module. for linprocfs module the > message is "symbol tsleep undefined". these modules are necessary > for VMWare 2.0 port. Your modules are out of synch with your kernel; tsleep() is now a macro wrapper for msleep(). Rebuild your modules and they'll be all right. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Fri, Nov 17, 2000 at 12:55:28PM +0100, Soren Schmidt wrote: > > I thought I was the only one, since my question on the freebsd-current > > mailing list went unanswered. > > You are _not_ alone, there has been numerous complains about this > on the list, but so far they have not been taken seriously :| One of my non-SMP machines reliably wedges whenever I do heavy disk I/O. I can't break to debugger. Nov 4 15:46:41 mollari /boot/kernel/kernel: atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 Nov 4 15:46:41 mollari /boot/kernel/kernel: ata0: at 0x1f0 irq 14 on atapci0 Nov 4 15:46:41 mollari /boot/kernel/kernel: ahc0: port 0xfc00-0xfcff mem 0xffbeb000-0xffbebfff irq 15 at device 11.0 on pci0 Nov 4 15:46:41 mollari /boot/kernel/kernel: aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Kris PGP signature
Re: CURRENT is freezing again ...
Warner Losh writes: > In message <[EMAIL PROTECTED]> Sheldon Hearn writes: > : The problem with a hard lock-up out of which you can't escape into the > : debugger is that it makes meaningful bug reports impossible. My non-SMP > : workstation has exhibited apparently arbitrary lock-ups since the advent > : of SMPng. > > You can also short IOCHK to ground to get an NMI which kicks you into > the debugger, even in an interrupt context. I have a card I built > from an old multi-function card to do this. I think it is A1 and A2, > but I don't have my ISA bus spec handy. Or you can use an alpha; most of which have a halt button that will drop you into the SRM console. ;) Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
missing interrupts (was Re: CURRENT is freezing again ...)
Valentin Chopov writes: > Hi, > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > 10 min after boot... > I've seen one similar problem on an alpha UP1000 that I'd like some input about. The UP1000 is essentially an alpha 21264 stuffed into an AMD Athlon system. It has an AMD-751 chipset and handles all device interrupts via an isa interrupt controller. I've noticed that under "heavy" load (gdb -k kernel.debug /dev/mem on an NFS filesystem), the network interface goes away, never to reappear. All I see is "fxp0: device timeout" on console. This started with SMPng. After a little bit of investigation with ddb, I discovered that the NIC's irq was pending. Eg: login: fxp0: device timeout Stopped at siointr1+0x17c: br zero,siointr1+0x32c db> call isa_irq_pending() 0x410 The fxp interface is at ir10, so 0x410 means there's an irq 10 pending. I then wrote a hack which sends an eoi. If I call my hack from ddb and send an eoi for irq10, everything goes back to normal and the network interface is back. So, is it a race in the interrupt code, or is it something about how the code is structured? On the alpha at least, we get the irq, mask the irq and set the ithread runnable. When the (isa) ithread runs, it calls the interrupt handler and then sends an eoi. The interrupt is then unmasked. I've peeked at the linux code and noticed that they do things differently. They first mask the interrupt, and then send the eoi immediately -- before the handler runs. They then run the handler and unmask the interrupt. The seem to do this both on i386 and alpha. Does anybody have any ideas about this? Does something bad happen if you don't send an eoi in a reasonable amount of time? Drew -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
> : >You can also short IOCHK to ground to get an NMI which kicks you into > : >the debugger, even in an interrupt context. > : > : Bad news for you warner: On a too large sample of my newer > : motherboards this doesn't work anymore :-( > > There's also a pci signal that you can either pull up or pull down > that's supposed to give you the same results. I've never really > needed to know it. SERR behaviour is programmable and there is no standard for it. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
