Re: Stopping a DoS by patching aio calls in STABLE
In message <[EMAIL PROTECTED]>, Mike Tancsa wri tes: > > As a work around to preventing a local DoS in STABLE (PR 17152), it was > suggested to me by Alfred Perlstein that I "patch [my] kernel to make all > aio calls return ENOSYS". Does anyone have any suggestions as how to do > that ? I have a shell server that I am a little worried about because of > script kiddies :-( Take a look at spy. Though it only works under -CURRENT and won't solve your immediate problem, it's still a pretty neat concept. Spy can be found at http://www.freebsd.org/~abial/spy-0.1.tgz and the manual can be found at http://www.freebsd.org/~sheldonh/spy.4. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: interrupt timeout
- Original Message - From: "Archie Cobbs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, March 07, 2000 2:57 PM Subject: Help: interrupt timeout > My laptop running 3.4-RELEASE decided it doesn't want to boot. > It was uncleanly shut down via the power switch by someone > who thought they were shutting down a different machine. > > Now when it boots, running fsck gives this result: > [snip] > > # fsck / > > *** /dev/rwd0s3a > > *** Last Mounted on / > > *** Root file system > > *** Phase 1 - Check Blocks and Sizes > > wd0: interrupt timeout (status 58 error 0) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: Last time I say: interrupt timeout. Probably a portable PC. (status 50 error 1) > [snip] I'd try disabling the DMA - it *should* be accessible within the BIOS under IDE UDMA enable/disable, depending upon the m/board maunfacturer - it certainly is on my Inspiron 7500, but with Compaq's good luck! Regards -- A Johns KPI Logistics P/L To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Vinum vs Adaptec AIC 7890?
> I wasn't sure what you meant by ARRE or AWRE in this case either, and I > couldn't find them in the vinum docs. I don't think the kernel panicked, or > if it did, it couldn't write any logs. I think the controller just freaked > out or something. The worst part is the lack of availability of the > machine when this happens, anything you could provide that would help me > fix this would be very helpful. You mean to say you have built a machine with no serial ports? Go grab another box and attach the two via a null modem to each other. The monitoring box should use COM2 idealy, but it's no big deal. The PC to be monitored should be connected on COM1. Set the monitor to 9600 bps and whatever port you picked. You can use kermit to log to a file and then watch or screen to interact with the downed PC, assuming it drops to debug. Boot the kernel -P and disconnect the keyboard. All /dev/console activity appears out the serial port. Do test this config before using it though. You don't want important data spilling out the port without something to catch it. --- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. <[EMAIL PROTECTED]>| --- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Help: interrupt timeout
My laptop running 3.4-RELEASE decided it doesn't want to boot. It was uncleanly shut down via the power switch by someone who thought they were shutting down a different machine. Now when it boots, running fsck gives this result: > chip0: rev 0x01 on pci0.0.0 > chip1: rev 0x02 on pci0.7.0 > ide_pci0: rev 0x01 on pci0.7.1 > ... > wdc0 at 0x1f0-0x3f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, accel, dma, iordis > ... > # fsck / > *** /dev/rwd0s3a > *** Last Mounted on / > *** Root file system > *** Phase 1 - Check Blocks and Sizes > wd0: interrupt timeout (status 58 error 0) > wd0: wdtimeout DMA status 4 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout DMA status 4 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout DMA status 4 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout DMA status 4 > wd0: interrupt timeout (status 50 error 1) > wd0: wdtimeout DMA status 4 > wd0: Last time I say: interrupt timeout. Probably a portable PC. (status >50 error 1) Well, yes in fact it is a portable PC :-) It just seems to hang at this point, even though there seems to be disk activity (like it's continuously retrying). This machine has run fine under this kernel since I installed 3.4-REL a month ago or so. This same problem happens with the 3.4-REL GENERIC kernel. Before this, it was running fine with a 3.0++ kernel and never had this problem after many power cycles. Is there any hope in getting this machine to work again?? Howabout disabling DMA? Is there some way to do that? Thanks for any pointers.. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Help: interrupt timeout
I've had the same problem. Most people have told me that I have to replace the hard drive. I never had the problem before 3.4. Maybe that's just a coincidence, though. -- Chris Byrnes (CB5820) Network Engineer, High Stability Internet Services http://www.highstability.com On Mon, 6 Mar 2000, Archie Cobbs wrote: > My laptop running 3.4-RELEASE decided it doesn't want to boot. > It was uncleanly shut down via the power switch by someone > who thought they were shutting down a different machine. > > Now when it boots, running fsck gives this result: > > > chip0: rev 0x01 on pci0.0.0 > > chip1: rev 0x02 on pci0.7.0 > > ide_pci0: rev 0x01 on pci0.7.1 > > ... > > wdc0 at 0x1f0-0x3f7 irq 14 on isa > > wdc0: unit 0 (wd0): > > wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T 512 B/S > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (atapi): , removable, accel, dma, iordis > > ... > > # fsck / > > *** /dev/rwd0s3a > > *** Last Mounted on / > > *** Root file system > > *** Phase 1 - Check Blocks and Sizes > > wd0: interrupt timeout (status 58 error 0) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: interrupt timeout (status 50 error 1) > > wd0: wdtimeout DMA status 4 > > wd0: Last time I say: interrupt timeout. Probably a portable PC. (status >50 error 1) > > Well, yes in fact it is a portable PC :-) It just seems to hang > at this point, even though there seems to be disk activity (like > it's continuously retrying). > > This machine has run fine under this kernel since I installed > 3.4-REL a month ago or so. This same problem happens with the > 3.4-REL GENERIC kernel. > > Before this, it was running fine with a 3.0++ kernel and never > had this problem after many power cycles. > > Is there any hope in getting this machine to work again?? > Howabout disabling DMA? Is there some way to do that? > > Thanks for any pointers.. > -Archie > > ___ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
