Re: swap_pager: indefinite wait buffer?
At 09:53 AM 12/2/1999 -0600, Jim King wrote: Sorry if this doesn't belong on -stable, but I didn't get a response on -questions. I got this in my messages file: Dec 1 09:10:20 cgi /kernel: swap_pager: indefinite wait buffer: device: 0x20401, blkno: 776, size: 4096 Dec 1 09:11:31 cgi /kernel: swap_pager: indefinite wait buffer: device: 0x20401, blkno: 776, size: 4096 Dec 1 09:11:32 cgi last message repeated 2 times What exactly does this mean? I'm afraid that it means some disk hardware is flaking out. If that's the case how do I know which disk had the problem? (I have swap space on two drives.) OK, call me a doofus for not searching the mailing list archives. To answer my own question, this means that a pageout took longer than 20 seconds on device major 4, minor 0x20001, which happens to be /dev/da0s1b on my system (swap space on the first drive). The usual advice is that this is harmless. It does NOT indicate failing hardware. However, it does indicate a busy disk, and if it happens a lot you should probably add swap space on another drive (already done, unfortunately) and/or more memory. I saw this question a lot in the archives. Would this be a good one for the FAQ? Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
status of USB support in -stable
What is the status of USB in -stable? Can I expect problems connecting a USB printer to a FreeBSD 3.4 box? TIA, Martin P.S.: I've checked the list archives but couldn't answer this question myself. The FAQ at http://www.etla.net/~n_hibma/usb/FAQ.pl refers to 3.2 only. The 3.3 release notes only state that USB support has been improved. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
kernel not patching?
OK... in my ongoing strange saga, I added char *dgilbert_bre5_top = "dgilbert_bre5_top"; as a global variable in vinumraid5.c --- I'm doing this as part of a strategy to track down a memory (stack) corruption bug. Anyways... when I recompile the kernel, it compiles this one module... and this global variable is referenced. When I then search for this string (by lessing the kernel and searching for dgilbert), I can't find it in the kernel's image. What's up? Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel not patching?
David Gilbert once wrote: char *dgilbert_bre5_top = "dgilbert_bre5_top"; as a global variable in vinumraid5.c --- I'm doing this as part of a strategy to track down a memory (stack) corruption bug. Anyways... when I recompile the kernel, it compiles this one module... and this global variable is referenced. When I then search for this string (by lessing the kernel and searching for dgilbert), I can't find it in the kernel's image. What's up? Well, if you use vinum module, the string will not be in kernel, but in /modules/vinum.ko :) -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel not patching?
"Mikhail" == Mikhail Teterin [EMAIL PROTECTED] writes: Mikhail Well, if you use vinum module, the string will not be in Mikhail kernel, but in /modules/vinum.ko :) I have 'options vinum' in the kernel ... and typing 'make' give: [2:20:320]root@raid1:/sys/compile/RAID make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../dev/vinum/vinumraid5.c cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf setdef0.c cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf setdef1.c sh ../../conf/newvers.sh RAID cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf vers.c loading kernel Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel not patching?
On Thu, 2 Dec 1999, David Gilbert wrote: I have 'options vinum' in the kernel ... and typing 'make' give: pseudo-device vinum #Vinum concat/mirror/raid driver -- - 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-stable" in the body of the message
Re: kernel not patching?
On 1999-Dec-03 06:20:25 +1100, David Gilbert wrote: I have 'options vinum' in the kernel ... and typing 'make' give: I presume you read the warning in LINT: # Configuring Vinum into the kernel is not necessary, since the kld # module gets started automatically when vinum(8) starts. This # device is also untested. Use at your own risk. Maybe you should switch to using vinum as a KLD and see if your problem goes away. (BTW, auto char *foo = "foo"; means that the stack contains a pointer to a string foo. The string will be in static storage - ie to find the stack, you need to work out the KVA for "foo" and then search for this address). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel not patching?
"Peter" == Peter Jeremy [EMAIL PROTECTED] writes: Peter (BTW, auto char *foo = "foo"; means that the stack contains a Peter pointer to a string foo. The string will be in static storage Peter - ie to find the stack, you need to work out the KVA for "foo" Peter and then search for this address). Mmm knew that. May not have hacked kernel too much, but I have a fair grasp of C uglyness. the char *foo was put in as a global to check the value of the char foo[]="foostring" that I put into the functions. Now... this is not strictly C-legal, but with gcc, it will autosize foo[] and copy "foostring" into it. The cool thing is that sizeof(foo) == strlen(foo)+1. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel not patching?
OK... in my ongoing strange saga, I added char *dgilbert_bre5_top = "dgilbert_bre5_top"; as a global variable in vinumraid5.c --- I'm doing this as part of a strategy to track down a memory (stack) corruption bug. Anyways... when I recompile the kernel, it compiles this one module... and this global variable is referenced. When I then search for this string (by lessing the kernel and searching for dgilbert), I can't find it in the kernel's image. What's up? Module != kernel -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: swap_pager: indefinite wait buffer?
I saw this question a lot in the archives. Would this be a good one for the FAQ? Any question you see a lot in the archives is, by definition, good for a FAQ entry. :-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
wierd SCSI error prevents dump?
I'm getting the following error after a panic... it appears to be preventing the system from dumping. Is there anything I can do to help this? syncing disks... Timedout SCB handled by another timeout Timedout SCB handled by another timeout Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel compile succeeds but is unusable, take two
It was suggested to me that I should post my config file along with the exact commands I issue to build my kernel so here they are. # devicenpx0at isa? port IO_NPX irq 13 device npx0at isa? port IO_NPX Why did you do this? You MUST NOT dink with this line. # pseudo-device pty 16 Taking pty's out is a bad idea too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel compile succeeds but is unusable, take two
On Thu, 2 Dec 1999, Ben WIlliams wrote: # devicenpx0at isa? port IO_NPX irq 13 device npx0at isa? port IO_NPX Why did you change this? # The following Ethernet NICs are all PCI devices. # device pn0 # Lite-On 82c168/82c169 (``PNIC'') device pn1 # second "Lite-On" ''PNIC'' Not needed, the code will make more as it needs them. pseudo-device loop pseudo-device ether # pseudo-device sl 1 # pseudo-device ppp 1 # pseudo-device tun 1 # pseudo-device pty 16 You didn't want to comment 'pty' out. [ yadda yadda yadda ] // something about npx0 being found on the mb // something about npx0 being an INT 16 device supervisor read, page not present I would have looked at the npx0 device that you changed, and then reverted the change. That's just the logical approach though. -- - 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-stable" in the body of the message
