Re: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/103841
Hi! This is still the problem for recent 6.2-STABLE and BIOS version 1479, and the patch in the Audit-Trail still solves it. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator tester wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You're correct. I removed lnc from the kernel config and added le, then recompiled the kernel. No more kernel messages about network interfaces. Joe Holden wrote: Nathan Butcher wrote: Danny Braniss wrote: snip lnc0: Missed packet -- no receive buffer Not sure what the cause was. Perhaps I was just thrashing out my virtual NIC... Yeah, thats an issue with the default vmware emulated nic... Ta, Joe -BEGIN PGP SIGNATURE- iD8DBQFGbPFocuckYiL1ACcRAs9DAKDlUlVZRZYEQdL+Vvwul4MkMpdpMACgoMKZ D8Qek1kksPGfij0fDTFuIe4= =/J8n -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Server setup as a Diskless Server on reboot sends DHCP Discover packets out
Thanks Oliver, This worked a charm :) Kim Attree Oliver Fromme wrote: Kim Attree wrote: I've setup a machine as a diskless server, using PXEBoot with ihc-dhcpd to offer dhcp and dhcp configuration information. I did a test reboot on the server, and found to my dismay that the server NIC's are sending out dhcp discover packets and trying to get an address. The NIC's IP info is captured correctly in /etc/rc.conf: [...] and the /etc/dhclient.conf file is empty. I thought maybe it was the /conf directory used in the diskless Root structure creation, so I renamed it out of the way, but that made no difference. I can't seem to find where the definition is that makes the NIC's ask for DHCP info. Shortened output of /var/run/dmesg.boot pertaining to the DHCP Discover packets: snip Sending DHCP Discover packet from interface bge0 (00:0b:db:e6:a9:33) Sending DHCP Discover packet from interface bge1 (00:0b:db:e6:a9:35) That's the kernel itself trying to perform BOOTP/DHCP. It does that before mounting the root file system (which might be mounted via NFS anyway, requiring an IP address to be obtained via BOOTP or DHCP). If you don't want that, then remove options BOOTP from your kernel config file and rebuild your kernel. Best regards Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards, RELENG_6, SMP
DM MD :Well, I can of course shut the kernel up, but kernel time stability is still my DM MD :concern. I run ntpd there and while sometimes it seems stable (well, sorta: DM MD :drift are within several seconds...) there are cases of half-a-minute time DM MD :steps. DM MD DM MD I think the only hope you have of getting the issue addressed is to DM MD run FreeBSD current. If you can reproduce the time slips under current DM MD the developers should be able to track the problem down and fix it. The DM MD code is so different between those two releases that they are going to DM MD have a hard time working the problem in FreeBSD-6. DM DM Well, quick compile'n'install HEAD into the swap does not reveal time slips for DM now. However, this is with WITNESS, I'll try to turn off most debugging kernel DM options and try again. Not perfect: `time make install clean' finished with === Cleaning for screen-4.0.3 21.671u 3.775s 0:28.95 87.8%-1542500797858546+3035018384651625k 3393131677337410024+8717906021891401862io 1045071671142449598pf+0w Also, in /var/log/messages Jun 11 06:56:52 ct-new ntpd[613]: time reset -320.107962 s Jun 11 07:15:00 ct-new ntpd[613]: time reset -1.401627 s ct-new# ntpq -c pe remote refid st t when poll reach delay offset jitter == cs3661.rinet.ru 192.38.7.240 2 u 354 1024 3775.305 -66314. 4321.47 ns.rinet.ru 130.207.244.240 2 u 365 1024 3776.913 -66316. 4305.33 whale.rinet.ru 195.2.64.5 2 u 358 1024 3777.939 -66308. 4304.90 Any directions to debug this? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libtiff, spandsp
olivier.taylor [EMAIL PROTECTED] wrote: after having install libtiff, I am trying to install spandsp and get the following error : configure: error: Can't build without libtiff (does your system require a libtiff-devel package?) Look for that error message in the configure.log file and check what command exactly failed (whether it's missing a library or include file, or a certain symbol within an existing library, or whatever). Unfortunately, gnu configure sucks pretty much and is not very good at helping to debug failures. Building programs would often be easier without gnu configure. :-( Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards, RELENG_6, SMP
On Sat, 9 Jun 2007, Matthew Dillon wrote:
MD :Well, I can of course shut the kernel up, but kernel time stability is
still my
MD :concern. I run ntpd there and while sometimes it seems stable (well,
sorta:
MD :drift are within several seconds...) there are cases of half-a-minute time
MD :steps.
MD
MD If you don't want to do that, try forcing the timer to use the 8254
MD and see if that helps. You may also have to reduce the system tick
MD to ~100-200 hz.
Does not help either:
ct-new# sysctl kern.clockrate
kern.clockrate: { hz = 200, tick = 5000, profhz = 133, stathz = 26 }
ct-new# sysctl kern.timecounter
kern.timecounter.tick: 1
kern.timecounter.choice: TSC(-100) ACPI-safe(1000) i8254(0) dummy(-100)
kern.timecounter.hardware: i8254
kern.timecounter.nsetclock: 3
kern.timecounter.ngetmicrotime: 6118
kern.timecounter.ngetnanotime: 0
kern.timecounter.ngetbintime: 0
kern.timecounter.ngetmicrouptime: 4741
kern.timecounter.ngetnanouptime: 30
kern.timecounter.ngetbinuptime: 485
kern.timecounter.nmicrotime: 1027
kern.timecounter.nnanotime: 96
kern.timecounter.nbintime: 1123
kern.timecounter.nmicrouptime: 804
kern.timecounter.nnanouptime: 0
kern.timecounter.nbinuptime: 60658
kern.timecounter.stepwarnings: 0
kern.timecounter.smp_tsc: 0
ct-new# ps
calcru: negative runtime of -1322717 usec for pid 4 (g_down)
calcru: negative runtime of -1322717 usec for pid 4 (g_down)
PID TT STAT TIME COMMAND
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
SUBSCRIBE
Michael R. Cook, GCFW Network Security Specialist Norton Healthcare, Information Services 502-629-8034 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - This message is confidential, intended only for the named recipient(s) and may contain information that is privileged or exempt from disclosure under applicable law. Any patient health information must be delivered immediately to intended recipient(s). If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender at either the e-mail address or telephone number above and discard this e-mail. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
There are some problems, first DDoS (hardware DDoS) in the system. I compile some program and when start it my system blocks and restart (tested and on other system 6.2-stable and again this DDoS). To prevent users from DDoS some systems i not going to upload this program in the web. The next DDoS (I don't know about his..) somebody (..any h4x0r) send every day to me hardware DDoS attack .. then my system full block and drop my interner connection, when i try to RE-ENABLE my connection to the DHCP server it's says connecting.. without any answer i think it's becouse my server is full blocked.. I have open this ports : 53(domain..standart..), 25(mail servers..), 80(apache), 110(mail servers..), 113(identd), 443(apache), (ircd), 6667(ircd), 7000(ircd), 9000(ircd) .. i can't find the DDoS.. please somebody to help me this hardware DDoS to my system. Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: [EMAIL PROTECTED] (~)]: date 0706111826.40 date: can't reach time daemon, time set locally Mon Jun 11 18:26:40 EEST 2007 [EMAIL PROTECTED] (~)]: date Mon Jun 11 18:23:55 EEST 2007 [EMAIL PROTECTED] (~)]: ..now example for nptdate: [EMAIL PROTECTED] (~)]: ntpdate otel.net 11 Jun 18:25:08 ntpdate[5157]: step time server 212.36.8.133 offset 218.607216 sec [EMAIL PROTECTED] (~)]: date Mon Jun 11 18:25:09 EEST 2007 but the original world time for my country is: 18:28:58... can somebody help me to fix this errors.. please! Thanks in advance. Best regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On 06/11/07 17:30, ExTaZyTi wrote: There are some problems, first DDoS (hardware DDoS) in the system. 'hardware DDoS'... funny thing! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
ExTaZyTi wrote this message on Mon, Jun 11, 2007 at 18:30 +0300: There are some problems, first DDoS (hardware DDoS) in the system. I compile some program and when start it my system blocks and restart (tested and on other system 6.2-stable and again this DDoS). Please email the FreeBSD security team w/ the program as per: http://www.freebsd.org/security/#how [...] Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: This is because the timezone you are using is incorrect. FreeBSD stores the system time in UTC and then converts to the local timezone. If you use the correct timezone (you can set this by running tzsetup) this should not be a problem. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell SAS5 Performance Issue
Bjoern A. Zeeb wrote: On Tue, 27 Mar 2007, Ivan Voras wrote: Richard Tector wrote: Is there any information I could obtain that would be of use to you in tracking this one down? You could maybe contact the driver's author(s) directly and ask them. See the AUTHORS section of the man page for details. you should have done your homework before saying this and you might have noticed something;-) To just add a me too; same kind of machine. I have been in contact with people the last three days mostly gathering information for them. And yes, the integrated curses based controller utility you can start during boot does not seem to have options to adjust caching behavior. At least I had not seen and option for that either. Unfortunately this machine will be shipped of the day after tomorrow so I won't be able to test anything new. I'll follow this thread and in case I can help with anything - let me know. /bz -- Bjoern A. Zeebbzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hey guys any updates on this? I'm experiencing the same issue win2kx64 environment slow I/O write (read about 65MB/sec) in RAID 1. There is no way to enable caching in the boot BIOS ... anyone hear plans for them to update a version that will allow us to configure these options? -- View this message in context: http://www.nabble.com/Dell-SAS5-Performance-Issue-tf3474648.html#a11065717 Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell SAS5 Performance Issue
dmose wrote: Bjoern A. Zeeb wrote: On Tue, 27 Mar 2007, Ivan Voras wrote: Richard Tector wrote: Is there any information I could obtain that would be of use to you in tracking this one down? You could maybe contact the driver's author(s) directly and ask them. See the AUTHORS section of the man page for details. you should have done your homework before saying this and you might have noticed something;-) To just add a me too; same kind of machine. I have been in contact with people the last three days mostly gathering information for them. And yes, the integrated curses based controller utility you can start during boot does not seem to have options to adjust caching behavior. At least I had not seen and option for that either. Unfortunately this machine will be shipped of the day after tomorrow so I won't be able to test anything new. I'll follow this thread and in case I can help with anything - let me know. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hey guys any updates on this? I'm experiencing the same issue win2kx64 environment slow I/O write (read about 65MB/sec) in RAID 1. There is no way to enable caching in the boot BIOS ... anyone hear plans for them to update a version that will allow us to configure these options? Are you asking about FreeBSD or Windows 2000? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell SAS5 Performance Issue
Scott Long-2 wrote: dmose wrote: Bjoern A. Zeeb wrote: On Tue, 27 Mar 2007, Ivan Voras wrote: Richard Tector wrote: Is there any information I could obtain that would be of use to you in tracking this one down? You could maybe contact the driver's author(s) directly and ask them. See the AUTHORS section of the man page for details. you should have done your homework before saying this and you might have noticed something;-) To just add a me too; same kind of machine. I have been in contact with people the last three days mostly gathering information for them. And yes, the integrated curses based controller utility you can start during boot does not seem to have options to adjust caching behavior. At least I had not seen and option for that either. Unfortunately this machine will be shipped of the day after tomorrow so I won't be able to test anything new. I'll follow this thread and in case I can help with anything - let me know. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hey guys any updates on this? I'm experiencing the same issue win2kx64 environment slow I/O write (read about 65MB/sec) in RAID 1. There is no way to enable caching in the boot BIOS ... anyone hear plans for them to update a version that will allow us to configure these options? Are you asking about FreeBSD or Windows 2000? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Either or (actually Windows2003server x64) I figured the write cache is not an OS specific setting, but rather controlled via the host adapters internal BIOS. So I can't see any way to enable this via the bios.. -- View this message in context: http://www.nabble.com/Dell-SAS5-Performance-Issue-tf3474648.html#a11066546 Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell SAS5 Performance Issue
dmose wrote: Scott Long-2 wrote: dmose wrote: Bjoern A. Zeeb wrote: On Tue, 27 Mar 2007, Ivan Voras wrote: Richard Tector wrote: Is there any information I could obtain that would be of use to you in tracking this one down? You could maybe contact the driver's author(s) directly and ask them. See the AUTHORS section of the man page for details. you should have done your homework before saying this and you might have noticed something;-) To just add a me too; same kind of machine. I have been in contact with people the last three days mostly gathering information for them. And yes, the integrated curses based controller utility you can start during boot does not seem to have options to adjust caching behavior. At least I had not seen and option for that either. Unfortunately this machine will be shipped of the day after tomorrow so I won't be able to test anything new. I'll follow this thread and in case I can help with anything - let me know. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hey guys any updates on this? I'm experiencing the same issue win2kx64 environment slow I/O write (read about 65MB/sec) in RAID 1. There is no way to enable caching in the boot BIOS ... anyone hear plans for them to update a version that will allow us to configure these options? Are you asking about FreeBSD or Windows 2000? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Either or (actually Windows2003server x64) I figured the write cache is not an OS specific setting, but rather controlled via the host adapters internal BIOS. So I can't see any way to enable this via the bios.. It's not controllable through the BIOS. There are Windows apps that will allow you to control it, but you should contact Dell and LSI about those, not FreeBSD. FreeBSD now has an option for handling it as well. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Jun 11, 2007, at 10:46 AM, Kevin K. wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS I'm not sure what the OP meant, but I can provide examples of a hardware DDoS. Way back when, certain machines were equipped with a Motorola/TI 56001 DSP, which had three separate, parallel execution units, and was an early example of SIMD/VLIW design. It turns out that if you issued an instruction to all three pipelines [1] which loaded or saved to the same memory address, you would fry the DSP chip. The compiler used to generate the code for the 56K DSP chip would prevent this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) -- -Chuck [1] IIRC, it could deal with two pipelines hitting the same address, but not all three. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On 6/11/07, Kevin K. [EMAIL PROTECTED] wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k It's very clear that English isn't his mother language, and he may means the DDoS he gets kills his box cpu ..etc. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Is your example not just a plain old Denial of Service (DoS) ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
Abdullah Ibn Hamad Al-Marri wrote: On 6/11/07, Kevin K. [EMAIL PROTECTED] wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k It's very clear that English isn't his mother language, and he may means the DDoS he gets kills his box cpu ..etc. May be because Otel.net is in Bulgaria I have the feeling that his mother language is bulgarian .. and his age is 11? :) Shame that google now hide the IP of the sender :( Now, if you explain little more about your problem and forget for the hardware DDOS we can help ? :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Jun 11, 2007, at 1:57 PM, Mike Tancsa wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Yes, it is. Is your example not just a plain old Denial of Service (DoS) ? Yes, as it stands. But if you ship this code to other machines, perhaps it would then qualify as being _Distributed_? :-) / 2 -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Monday 11 June 2007 18:05:59 Chuck Swiger wrote: On Jun 11, 2007, at 1:57 PM, Mike Tancsa wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Yes, it is. Is your example not just a plain old Denial of Service (DoS) ? Yes, as it stands. But if you ship this code to other machines, perhaps it would then qualify as being _Distributed_? :-) / 2 clever switch but still wrong ... DDoS is ONE target and multi-source but not multi-target and local source :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic: vm_fault: fault on nofault entry, addr: c1d9c000
For some time now, weeks, actually my FreeBSD box has been crashing aparrantly randomly. It took me forever but I finally managed to capture a dump! Here is what kgdb said: - Script started on Mon Jun 11 19:56:46 2007 kgdb kernel.debug /var/crash/vmcore.0 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd. Unread portion of the kernel message buffer: panic: vm_fault: fault on nofault entry, addr: c1d9c000 Uptime: 2d1h27m41s Dumping 351 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 351MB (89840 pages) 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) jhengis# ^D exit Script done on Mon Jun 11 19:56:59 2007 - I have never had to debug a kernel dump before, and frankly am unfamiliar with the procedure, Sorry if I have missed something obvious :( The crashes started *around* the time that I upgraded to Xorg 7.2, however I am unsure this is the cause, notwithstanding I *think* that something that got rebuilt during that period is causing the crash. It does not seem, however, to be Xorg itself; the crashes also occur when X is not in use. I did not rebuild my kernel around that time. I hope that I have provided enough information, if I have not, I can gladly get more. I have attached my kernel configuration, my uname -a output is: FreeBSD jhengis.vistua.com 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #3: Sat Jun 2 12:45:19 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BORODIN i386 (The recent datestamp on this kernel is because I rebuilt it with debug information, so I could catch the dump.) You can get the complete contents of /var/crash from ftp://[EMAIL PROTECTED]/pub/crash.tar.bz2 Any help would be greatly appreciated! --John machine i386 cpu I686_CPU ident BORODIN # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. makeoptions DEBUG=-g options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic# I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering device atapicam # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device
Re: calcru: runtime went backwards, RELENG_6, SMP
:== : cs3661.rinet.ru 192.38.7.240 2 u 354 1024 3775.305 -66314. 4321.47 : ns.rinet.ru 130.207.244.240 2 u 365 1024 3776.913 -66316. 4305.33 : whale.rinet.ru 195.2.64.5 2 u 358 1024 3777.939 -66308. 4304.90 : :Any directions to debug this? : :Sincerely, :D.Marck [DM5020, MCK-RIPE, DM3-RIPN] Since you are running on HEAD now, could you also kgdb the live kernel and print cpu_ticks? I believe the sequence is (someone correct me if I am wrong): kgdb /kernel /dev/mem print cpu_ticks As for further tests... try building a non-SMP kernel (i.e. one that only recognizes one cpu) and see if the problem occurs there. That will determine whether there is a basic problem with time keeping or whether it is an issue with SMP. I'm afraid there isn't much more I can do to help, other then to make suggestions on tests that you can run that will hopefully ring a bell with another developer. -Matt Matthew Dillon [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
* Mike Tancsa [EMAIL PROTECTED] [070611 13:58] wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Is your example not just a plain old Denial of Service (DoS) ? Well it takes 3 execution pipelines... -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
