Re: Dell SAS5 Performance Issue
On Tue, 17 Apr 2007, Matthew Jacob wrote: Hi, Is there any news on the performance of this card? I personally have not been able to reproduce the problem. It seems to occur whether in Integrated Raid or not. It seems to be related to specific backplanes and drives. It's an important problem to solve I agree. I had done some research a few weeks back and just found the reference again. There is a fujitsu-siemens manual[1], and 2.4.8 Disk write caching gives some hitns on why things are the way they are. I had also found references, that Windows people have effectively seen the same problem. My conclusion is - that's nothing that can be changes with software easily for the Dell PE 860 with that special chip. another 0.002ct References: [1] http://manuals.fujitsu-siemens.com/serverbooks/content/manuals/english/ir-sas-ug-en.pdf -- 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]
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
Hi! I believe the culprit is somewhere in a recent MFC to atapi-cam.c (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system hangs and INQUIRY ILLEGAL REQUEST errors here. I utillized the version of atapi-cam.c (rev. 1.42.2.1) and all works normally. vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default ad0: 114473MB WDC WD1200JB-00GVA0 08.02D08 at ata0-master UDMA100 acd0: DVDR HL-DT-ST DVDRAM GSA-4163B/A104 at ata1-master UDMA33 ad4: 152627MB WDC WD1600JD-00GBB0 02.05D02 at ata2-master SATA150 SMP: AP CPU #1 Launched! cd0 at ata1 bus 0 target 0 lun 0 cd0: HL-DT-ST DVDRAM GSA-4163B A104 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/mlxd0s1a GEOM_ELI: Device mlxd0s1b.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: software Best regards, Andrei V. Lavreniyuk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
Adrian Chadd wrote: I'm talking to someone about it who has some patches against -current. We'll see what can be done. Thankfully! The solution for FreeBSD looks doable without having to keep NAT state like TPROXY does.. Adrian just want to how's the progress regarding this issue. TIA Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tproxy on freebsd
zen wrote: Adrian Chadd wrote: I'm talking to someone about it who has some patches against -current. We'll see what can be done. Thankfully! The solution for FreeBSD looks doable without having to keep NAT state like TPROXY does.. Adrian sorry double post just want to _Know_ how's the progress regarding this issue. TIA Zen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Andrei V. Lavreniyuk said the following on 20.04.2007 12:27: Hi! On Thu, Apr 19, 2007 at 12:37:08PM -0700, pete wright wrote: ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default ad0: 114473MB WDC WD1200JB-00GVA0 08.02D08 at ata0-master UDMA100 acd0: DVDR HL-DT-ST DVDRAM GSA-4163B/A104 at ata1-master UDMA33 ad4: 152627MB WDC WD1600JD-00GBB0 02.05D02 at ata2-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 ^ ??? i assume you are asking what those errors mean you most likely have a bad cdrom in there, or the drive has an error. try a different disk, and if that fails try another drive. Are you sure the ATAPI command used at that time is attempting to read disc information and not, say, try to get drive capabilities? I'm lead to believe that the DVD drive he has doesn't support a particular ATAPI function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is Illegal field in CDB for most ATAPI operatons... Adding to my report: Test 1: To start k3b with a disk in the device of reading/record. A start takes a place normally. Test 2: To start k3b without a disk in the device of reading/record. At a start the k3b system hangs up and overloaded. After writing a disk with k3b and eject media from device - system freeze without any response. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLItAhLjVFCVp0wsRCg12AJwKvkPdR/ByCCBDSIS9J6k/tcxI5wCglUPG UxuVBFv7UoZJcKEK9nhafBs= =XvA5 -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: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Andrei V. Lavreniyuk said the following on 20.04.2007 10:10: Hi! ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default ad0: 114473MB WDC WD1200JB-00GVA0 08.02D08 at ata0-master UDMA100 acd0: DVDR HL-DT-ST DVDRAM GSA-4163B/A104 at ata1-master UDMA33 ad4: 152627MB WDC WD1600JD-00GBB0 02.05D02 at ata2-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 ^ ??? i assume you are asking what those errors mean you most likely have a bad cdrom in there, or the drive has an error. try a different disk, and if that fails try another drive. Are you sure the ATAPI command used at that time is attempting to read disc information and not, say, try to get drive capabilities? I'm lead to believe that the DVD drive he has doesn't support a particular ATAPI function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is Illegal field in CDB for most ATAPI operatons... Kernel from March works normally... I have the same problem on my 6.2-STABLE box: acd0: DVDR ASUS DRW-1604P/1.09 at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 And kernel from beginning of March works normally too. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLIkVhLjVFCVp0wsRCkKiAKCb3K/5u/60mYr3TJZW5r6BbFU72gCg6iMG Ckb0FZGCE5QkqGZeltPA1Vs= =vUJq -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: No buffer space available
On Sat, Apr 07, 2007 at 08:20:58PM -0300, Marc G. Fournier wrote: - --On Saturday, April 07, 2007 20:12:00 +0100 Chris [EMAIL PROTECTED] wrote: Also to add I now have a 2nd box using 6.2 STABLE few days old code, had to use it because of broadcom 5755 nic card, I plan to use large tcp window sizes so will be interesting to see if this also suffers from the problem. I've got 8 servers on the same network, 3 are almost identical, but one of them (the one with the problem) is using software RAID vs hardware ... but, if you are seeing it without using software RAID, then that is obviously not the culprit :( May be a red herring... I'm able to reproduce the No buffer space available message when setting net.inet.tcp.(send|recv)space to non-default values. All I've tried is the following, with a kernel dated 2007/04/22: # sysctl net.inet.tcp.sendspace=131072 # sysctl net.inet.tcp.recvspace=262144 Example session: $ su2 # sysctl net.inet.tcp.sendspace=131072 net.inet.tcp.sendspace: 32768 - 131072 # sysctl net.inet.tcp.recvspace=262144 net.inet.tcp.recvspace: 65536 - 262144 # logout $ ssh medusa socket: No buffer space available ssh: connect to host medusa port 22: No buffer space available $ su2 # sysctl net.inet.tcp.sendspace=32768 net.inet.tcp.sendspace: 131072 - 32768 # sysctl net.inet.tcp.recvspace=65536 net.inet.tcp.recvspace: 262144 - 65536 # logout $ ssh medusa Last login: Mon Apr 23 03:45:45 2007 from ... I assume this is because the maximum size of a TCP datagram is 65536 bytes, but as I'm not familiar enough with TCP on such a low level, this may be speculation on my part. Just something worth checking/tinkering with. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-STABLE deadlock?
On Mon, Apr 23, 2007 at 03:56:32AM +0100, Adrian Wontroba wrote: On Tue, Mar 13, 2007 at 02:08:48PM +, Adrian Wontroba wrote: At work, amoungst my stable of old computers running FreeBSD, I have a Fujitsu M800 - a 4 Zeon SMP processor with 4 GB of memory. This primarily runs Nagios and a small and lightly used MySQL database, along with a few inbound FTP transfers per minute. It has a Mylex card based disc subsystem, ruling out crash dumps. At some point during 5.5-STABLE this machine started to occasionally hang ... Another 6-STABLE (cvsupped on 27/03/07) example, with diagnostics taken rather sooner after the hang. Processes with wmesg=ufs feature often in the ps output. http://www.stade.co.uk/crash1/ I would suspect the mlx controller. There is several processes (for instance, 988, 50918) waiting for completion of block read, and processes in the ufs states are the result of the lock cascade, IMHO. pgpToTKzpBFHu.pgp Description: PGP signature
Re: Fatal trap 12: page fault while in kernel mode
On Thu, Apr 19, 2007 at 04:14:23PM +0200, Christian Walther wrote: On 19/04/07, Kai [EMAIL PROTECTED] wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi Again, The panics keep happening, so I'm trying alternate kernel setups. This is a trace of a panic on a default SMP kernel with debugging symbols. I'm At a loss on how to progress at this point, perhaps someone can help me please? [snip] Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9cf938 frame pointer = 0x28:0xeb9cf944 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 13577 (perl5.8.8) trap number = 12 panic: page fault Is this perl derived from ports? And if so, did you rebuild it after you upgraded to 6.2? Or is maybe FreeBSD 4.x binary compatibility missing from your kernel? Hi Chris, Thanks for your reply; The upgrade i'm talking about is just a term describing that we switched from FreeBSD 4.10 to 6.2. Its new hardware; its hardware on which FreeBSD 4.10 will not run. So in effect its not an upgrade, though the symptoms did not show on apache-1.3.37 + nfsmounted homepages under FreeBSD 4.10. If perl would be the problem, the OS shouldn't panic IMHO. Perl in this case is writing a fairly large guestbook file (eg. 2 Mb), and does this through perls own: open(BOOK, +$file) or die; This $file is located on an NFS mounted filesystem. It'll get read and written. The NFS filesystem is mounted with rw,nosuid,intr,bg,resvport,nfsv3. I have tried mounting without intr, but panics keep happening. The NFS server is a Netapp filer. This is a production environment, so I can't go updating to the latest current. Kai -- This was an above the .signature production ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
Hi,
Recently I have noticed that one of our Dell PE1950's has been crashing
a lot with the following reason supervisor read, page not present.
The system runs 6.2 Release under i386.
I have attached 2 back traces, and I still have both cores if any more
information is required. Any light that can be shed on this problem
would be greatly appreciated.
Tom
===
uname -a
FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon
Apr 2 20:13:11 BST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE1950 i386
## Core 1
[EMAIL PROTECTED] '13:14:47' '/home/london/tj'
$ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1
[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:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x15c
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05df61f
stack pointer = 0x28:0xe4f63c30
frame pointer = 0x28:0xe4f63c90
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 12 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1h25m33s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887
7arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK)
7arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK)
1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663
1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439
1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215
1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975
959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687
671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399
383 367 351 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 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc05622ba in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc05625e1 in panic (fmt=0xc06e2578 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc06b4580 in trap_fatal (frame=0xe4f63bf0, eva=16777308) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc06b42bf in trap_pfault (frame=0xe4f63bf0, usermode=0,
eva=16777308) at /usr/src/sys/i386/i386/trap.c:745
#5 0xc06b3f19 in trap (frame=
{tf_fs = -1067581432, tf_es = -965803992, tf_ds = -964624344,
tf_edi = -957112288, tf_esi = -965676032, tf_ebp = -453624688, tf_isp =
-453624804, tf_ebx = 16777216, tf_edx = -968955648, tf_ecx = 4, tf_eax =
0, tf_trapno = 12, tf_err = 0, tf_eip = -1067583969, tf_cs = 32,
tf_eflags = 66118, tf_esp = 3, tf_ss = 0}) at
/usr/src/sys/i386/i386/trap.c:435
#6 0xc06a095a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc05df61f in in_arpinput (m=0xc68ba200) at
/usr/src/sys/netinet/if_ether.c:636
#8 0xc05df4ea in arpintr (m=0xc68ba200) at
/usr/src/sys/netinet/if_ether.c:551
#9 0xc05d861b in netisr_processqueue (ni=0xc076b078) at
/usr/src/sys/net/netisr.c:236
#10 0xc05d881a in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:349
#11 0xc054cc49 in ithread_execute_handlers (p=0xc63ed860, ie=0xc643bb80)
at /usr/src/sys/kern/kern_intr.c:682
#12 0xc054cd59 in ithread_loop (arg=0xc63bb870) at
/usr/src/sys/kern/kern_intr.c:765
#13 0xc054b9fd in fork_exit (callout=0xc054cd04 ithread_loop,
arg=0xc63bb870, frame=0xe4f63d38) at /usr/src/sys/kern/kern_fork.c:821
#14 0xc06a09bc in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
(kgdb) exit
Undefined command: exit. Try help.
(kgdb) quit
## Core 2
[EMAIL PROTECTED] '13:15:32' '/home/london/tj'
$ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.0
[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
Re: Fatal trap 12: page fault while in kernel mode
Kai wrote: On Thu, Apr 19, 2007 at 04:14:23PM +0200, Christian Walther wrote: On 19/04/07, Kai [EMAIL PROTECTED] wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi Again, The panics keep happening, so I'm trying alternate kernel setups. This is a trace of a panic on a default SMP kernel with debugging symbols. I'm At a loss on how to progress at this point, perhaps someone can help me please? [snip] Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9cf938 frame pointer = 0x28:0xeb9cf944 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 13577 (perl5.8.8) trap number = 12 panic: page fault Is this perl derived from ports? And if so, did you rebuild it after you upgraded to 6.2? Or is maybe FreeBSD 4.x binary compatibility missing from your kernel? Hi Chris, Thanks for your reply; The upgrade i'm talking about is just a term describing that we switched from FreeBSD 4.10 to 6.2. Its new hardware; its hardware on which FreeBSD 4.10 will not run. So in effect its not an upgrade, though the symptoms did not show on apache-1.3.37 + nfsmounted homepages under FreeBSD 4.10. If perl would be the problem, the OS shouldn't panic IMHO. Perl in this case is writing a fairly large guestbook file (eg. 2 Mb), and does this through perls own: open(BOOK, +$file) or die; This $file is located on an NFS mounted filesystem. It'll get read and written. The NFS filesystem is mounted with rw,nosuid,intr,bg,resvport,nfsv3. I have tried mounting without intr, but panics keep happening. The NFS server is a Netapp filer. This is a production environment, so I can't go updating to the latest current. Kai Just a me too, however I seem to get these crashes from random applications. See my last post for back traces. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] problem hal - k3b ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ganbold said the following on 23.04.2007 05:39: Beni wrote: On Friday 20 April 2007 03:55:56 Ganbold wrote: Michael Nottebrock wrote: I forwarded my mail to gnome@ (the HAL maintainers) after sending it and Joe Marcus Clarke from gnome@ had this to say on the issue: --- snip This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe --- snip Beni, Robert, Ganbold, are you all in fact running the latest version of the hal port and do you all have atapicam enabled in your kernel? If not, making sure of both might help avoiding the problem. I see. I know I have updated my system last Saturday (14th April 2007) and I think I updated both hal and kdelibs ports. I have atapicam enabled in kernel. Let me double check it this weekend and I will let you know. thanks, Ganbold Subject: Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? From: Joe Marcus Clarke [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 12:49:26 -0400 To: Michael Nottebrock [EMAIL PROTECTED] To: Michael Nottebrock [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Michael Nottebrock wrote: I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but just FYI. Subject: Re: [kde-freebsd] problem hal - k3b ? From: Michael Nottebrock [EMAIL PROTECTED] Date: Thu, 19 Apr 2007 18:12:46 +0200 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Beni [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Wednesday, 18. April 2007, Beni wrote: Hi List, I think I have a problem with hal(d) and k3b (version 1.0 from ports) : my whole system freezes when starting up k3b. I get the splash screen and then it all stops and a ctrl-alt-del is the only way out. Other people have reported kernel panics. It looks to me like k3b's device probing and hald's device probing at the same time manages to tickle a bug in ata(4). Ref: http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.htm l http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html I'm afraid a true kernel hacker will have to inconvenince themselves with running k3b and hal in order to have this one fixed. FWIW, I haven't seen in happening on 5.5. This should have been fixed a while ago by jylefort when he set the default device for ATAPI access to be the ATAPICAM device (as opposed to the ATA device). Assuming you have not undone that change, and are running the latest version of HAL, these panics should not be occurring. Even still, you're right that these are not HAL bugs, but rather an issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, and dvd-utils under the covers to do the actual device work. Not sure what k3b is using, but maybe it diddles something it shouldn't. Joe Could it all be related to this : http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034553.html and the solution from Shane Bell in http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034602.html : I believe the culprit is somewhere in a recent MFC to atapi-cam.c (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system hangs and INQUIRY ILLEGAL REQUEST errors here. Most probably. I updated everything, including source and ports on April 22nd and the problem still exists. k3b hangs after loading splash screen and I had to use power button on my laptop to power down and up the system. I will try to revert rev 1.42.2.2 and see what will happen. This problem appear in my system after updating system and ports on April, 06. K3b hangs either after loading splash screen or after eject wrote media from device. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Port Compile Error: mod_security2
Hey guys, Running 6.2-RELEASE-p3 and apache2.2.4. I'm trying to install mod_security2 from ports, and I'm getting the following error during the build http://Schiz0.securityexploits.com/mod_security2.ports.compile.error I've updated the ports database via csup within 24 hours of trying to compile mod_security2, so it isn't an outdated database. uname -a: FreeBSD Schiz0.securityexploits.com 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3#0: Sun Apr 15 23:22:36 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SCHIZ0NET i386 Thanks in advance! ~Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal trap 12: page fault while in kernel mode
On Thu, Apr 19, 2007 at 02:33:29PM +0200, Kai wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi Again, The panics keep happening, so I'm trying alternate kernel setups. This is a trace of a panic on a default SMP kernel with debugging symbols. snip Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34 ^ fault code = supervisor read, page not present ^^^ #7 0xc06bdefa in vfs_vmio_release (bp=0xdbec2560) at atomic.h:146 #8 0xc06be728 in getnewbuf (slpflag=0, slptimeo=0, size=6585, maxsize=8192) at ../../../kern/vfs_bio.c:1779 #9 0xc06bfccc in getblk (vp=0xca2cfdd0, blkno=8438, size=6585, slpflag=0, slptimeo=0, flags=0) at ../../../kern/vfs_bio.c:2497 #10 0xc075ad41 in nfs_getcacheblk (vp=0xca2cfdd0, bn=8438, size=6585, td=0xc8cd1c00) at ../../../nfsclient/nfs_bio.c:1261 #11 0xc075a978 in nfs_write (ap=0x0) at ../../../nfsclient/nfs_bio.c:1069 #12 0xc089fde6 in VOP_WRITE_APV (vop=0xc0984440, a=0xeb9cfbec) at vnode_if.c:698 #13 0xc06dbb26 in vn_write (fp=0xc8940e10, uio=0xeb9cfcbc, active_cred=0xc89ee880, flags=0, td=0xc8cd1c00) at vnode_if.h:372 #14 0xc0698f63 in dofilewrite (td=0xc8cd1c00, fd=5, fp=0xc8940e10, auio=0xeb9cfcbc, offset=Unhandled dwarf expression opcode 0x93 ) at file.h:252 #15 0xc0698e07 in kern_writev (td=0xc8cd1c00, fd=5, auio=0xeb9cfcbc) at ../../../kern/sys_generic.c:402 #16 0xc0698d2d in write (td=0xc8cd1c00, uap=0xc8cd1c00) at ../../../kern/sys_generic.c:326 I believe I am seeing the same panic on my samba servers, sometimes from NFS and sometimes from FFS. I see it on i386 and amd64 alike. I do not know how to manually trigger it, but I do have two servers sitting in DDB from after the panic, waiting for more experienced hands to continue the debugging from what I have already done. I filed a PR with as much details as I could think of, and it would be wonderful if someone could look at it and either tell me what else to do in DDB, or I could provide remote access to the existing DDB session to a developer. Both servers crashed in vfs_vmio_release but one was through NFS and one through FFS. pr 111831 http://docs.freebsd.org/cgi/mid.cgi?200704181924.l3IJOMUL088901 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Compile Error: mod_security2
Check your PCRE package: $ pkg_info -L pcre-6.6_1|grep -i pcre.c /usr/local/man/man3/pcre_compile.3.gz /usr/local/man/man3/pcre_compile2.3.gz /usr/local/man/man3/pcre_config.3.gz /usr/local/man/man3/pcre_copy_named_substring.3.gz /usr/local/man/man3/pcre_copy_substring.3.gz /usr/local/bin/pcre-config [...snip...] /usr/local/include/pcre.h ~BAS On Mon, 2007-04-23 at 10:17 -0400, Schiz0 wrote: Hey guys, Running 6.2-RELEASE-p3 and apache2.2.4. I'm trying to install mod_security2 from ports, and I'm getting the following error during the build http://Schiz0.securityexploits.com/mod_security2.ports.compile.error I've updated the ports database via csup within 24 hours of trying to compile mod_security2, so it isn't an outdated database. uname -a: FreeBSD Schiz0.securityexploits.com 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3#0: Sun Apr 15 23:22:36 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SCHIZ0NET i386 Thanks in advance! ~Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No buffer space available
On Monday, 23 April 2007 at 4:06:10 -0700, Jeremy Chadwick wrote: On Sat, Apr 07, 2007 at 08:20:58PM -0300, Marc G. Fournier wrote: - --On Saturday, April 07, 2007 20:12:00 +0100 Chris [EMAIL PROTECTED] wrote: Also to add I now have a 2nd box using 6.2 STABLE few days old code, had to use it because of broadcom 5755 nic card, I plan to use large tcp window sizes so will be interesting to see if this also suffers from the problem. I've got 8 servers on the same network, 3 are almost identical, but one of them (the one with the problem) is using software RAID vs hardware ... but, if you are seeing it without using software RAID, then that is obviously not the culprit :( May be a red herring... I'm able to reproduce the No buffer space available message when setting net.inet.tcp.(send|recv)space to non-default values. All I've tried is the following, with a kernel dated 2007/04/22: # sysctl net.inet.tcp.sendspace=131072 # sysctl net.inet.tcp.recvspace=262144 Example session: $ su2 # sysctl net.inet.tcp.sendspace=131072 net.inet.tcp.sendspace: 32768 - 131072 # sysctl net.inet.tcp.recvspace=262144 net.inet.tcp.recvspace: 65536 - 262144 # logout $ ssh medusa socket: No buffer space available ssh: connect to host medusa port 22: No buffer space available $ su2 # sysctl net.inet.tcp.sendspace=32768 net.inet.tcp.sendspace: 131072 - 32768 # sysctl net.inet.tcp.recvspace=65536 net.inet.tcp.recvspace: 262144 - 65536 # logout $ ssh medusa Last login: Mon Apr 23 03:45:45 2007 from ... I assume this is because the maximum size of a TCP datagram is 65536 bytes, but as I'm not familiar enough with TCP on such a low level, this may be speculation on my part. Just something worth checking/tinkering with. Try to adjust kern.ipc.maxsockbuf value. -- == - Best regards, Nikolay Pavlov. --- == ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal trap 12: page fault while in kernel mode
On Thu, Apr 19, 2007 at 02:33:29PM +0200, Kai wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi all, To continue this story, a colleague wrote a small program in C that launches 40 threads to randomly append and write to 10 files on an NFS mounted filesystem. If I keep removing the files on one of the other machines in a while loop, the first system panics: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9f69b8 frame pointer = 0x28:0xeb9f69c4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 73626 (nfscrash) trap number = 12 panic: page fault cpuid = 1 Uptime: 3h2m14s Sounds like a nice denial of service problem. I can hand the program to developers on request. Regards, Kai Storbeck -- This was an above the .signature production ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
Are you running i386 on this platform to keep your network platform homogeneous. We run 6.2p2 on amd64 on the same hardware w/o issue. That's an interesting ARP issue; are you using bce(4)? We prefer to stack the machine with PCIe4x em(4) cards. ~BAS On Mon, 2007-04-23 at 13:24 +0100, Tom Judge wrote: I have attached 2 back traces, and I still have both cores if any more -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal trap 12: page fault while in kernel mode
On Mon, Apr 23, 2007 at 01:27:27PM +0100, Tom Judge wrote: Kai wrote: On Thu, Apr 19, 2007 at 04:14:23PM +0200, Christian Walther wrote: On 19/04/07, Kai [EMAIL PROTECTED] wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi Again, The panics keep happening, so I'm trying alternate kernel setups. This is a trace of a panic on a default SMP kernel with debugging symbols. I'm At a loss on how to progress at this point, perhaps someone can help me please? [snip] Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9cf938 frame pointer = 0x28:0xeb9cf944 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 13577 (perl5.8.8) trap number = 12 panic: page fault Is this perl derived from ports? And if so, did you rebuild it after you upgraded to 6.2? Or is maybe FreeBSD 4.x binary compatibility missing from your kernel? Hi Chris, Thanks for your reply; The upgrade i'm talking about is just a term describing that we switched from FreeBSD 4.10 to 6.2. Its new hardware; its hardware on which FreeBSD 4.10 will not run. So in effect its not an upgrade, though the symptoms did not show on apache-1.3.37 + nfsmounted homepages under FreeBSD 4.10. If perl would be the problem, the OS shouldn't panic IMHO. Perl in this case is writing a fairly large guestbook file (eg. 2 Mb), and does this through perls own: open(BOOK, +$file) or die; This $file is located on an NFS mounted filesystem. It'll get read and written. The NFS filesystem is mounted with rw,nosuid,intr,bg,resvport,nfsv3. I have tried mounting without intr, but panics keep happening. The NFS server is a Netapp filer. This is a production environment, so I can't go updating to the latest current. Kai Just a me too, however I seem to get these crashes from random applications. See my last post for back traces. Just to clarify, your problem appears to have nothing to do with the above report. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal trap 12: page fault while in kernel mode
On Mon, Apr 23, 2007 at 05:35:47PM +0200, Kai wrote: On Thu, Apr 19, 2007 at 02:33:29PM +0200, Kai wrote: On Wed, Apr 11, 2007 at 12:53:32PM +0200, Kai wrote: Hello all, We're running into regular panics on our webserver after upgrading from 4.x to 6.2-stable: Hi all, To continue this story, a colleague wrote a small program in C that launches 40 threads to randomly append and write to 10 files on an NFS mounted filesystem. If I keep removing the files on one of the other machines in a while loop, the first system panics: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06bdefa stack pointer = 0x28:0xeb9f69b8 frame pointer = 0x28:0xeb9f69c4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 73626 (nfscrash) trap number = 12 panic: page fault cpuid = 1 Uptime: 3h2m14s Sounds like a nice denial of service problem. I can hand the program to developers on request. Please send it to me. Panics are always much easier to get fixed if they come with a test case that developer can use to reproduce it. Kris pgplSEXbF4bW4.pgp Description: PGP signature
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote:
Hi,
Recently I have noticed that one of our Dell PE1950's has been crashing
a lot with the following reason supervisor read, page not present.
The system runs 6.2 Release under i386.
I have attached 2 back traces, and I still have both cores if any more
information is required. Any light that can be shed on this problem
would be greatly appreciated.
Tom
===
uname -a
FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon
Apr 2 20:13:11 BST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE1950 i386
## Core 1
[EMAIL PROTECTED] '13:14:47' '/home/london/tj'
$ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1
[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:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x15c
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05df61f
stack pointer = 0x28:0xe4f63c30
frame pointer = 0x28:0xe4f63c90
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 12 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1h25m33s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887
7arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK)
7arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK)
You might be hitting a bug in an obscure code path because of the
above errors. I'm CC'ing someone who might be able to help.
Kris
1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663
1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439
1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215
1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975
959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687
671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399
383 367 351 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 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc05622ba in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc05625e1 in panic (fmt=0xc06e2578 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc06b4580 in trap_fatal (frame=0xe4f63bf0, eva=16777308) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc06b42bf in trap_pfault (frame=0xe4f63bf0, usermode=0,
eva=16777308) at /usr/src/sys/i386/i386/trap.c:745
#5 0xc06b3f19 in trap (frame=
{tf_fs = -1067581432, tf_es = -965803992, tf_ds = -964624344,
tf_edi = -957112288, tf_esi = -965676032, tf_ebp = -453624688, tf_isp =
-453624804, tf_ebx = 16777216, tf_edx = -968955648, tf_ecx = 4, tf_eax =
0, tf_trapno = 12, tf_err = 0, tf_eip = -1067583969, tf_cs = 32,
tf_eflags = 66118, tf_esp = 3, tf_ss = 0}) at
/usr/src/sys/i386/i386/trap.c:435
#6 0xc06a095a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc05df61f in in_arpinput (m=0xc68ba200) at
/usr/src/sys/netinet/if_ether.c:636
#8 0xc05df4ea in arpintr (m=0xc68ba200) at
/usr/src/sys/netinet/if_ether.c:551
#9 0xc05d861b in netisr_processqueue (ni=0xc076b078) at
/usr/src/sys/net/netisr.c:236
#10 0xc05d881a in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:349
#11 0xc054cc49 in ithread_execute_handlers (p=0xc63ed860, ie=0xc643bb80)
at /usr/src/sys/kern/kern_intr.c:682
#12 0xc054cd59 in ithread_loop (arg=0xc63bb870) at
/usr/src/sys/kern/kern_intr.c:765
#13 0xc054b9fd in fork_exit (callout=0xc054cd04 ithread_loop,
arg=0xc63bb870, frame=0xe4f63d38) at /usr/src/sys/kern/kern_fork.c:821
#14 0xc06a09bc in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
(kgdb) exit
Undefined command: exit. Try help.
(kgdb) quit
## Core 2
[EMAIL PROTECTED] '13:15:32' '/home/london/tj'
$ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.0
[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
Re: Port Compile Error: mod_security2
On 4/23/07, Schiz0 [EMAIL PROTECTED] wrote: Hey guys, Running 6.2-RELEASE-p3 and apache2.2.4. I'm trying to install mod_security2 from ports, and I'm getting the following error during the build http://Schiz0.securityexploits.com/mod_security2.ports.compile.error I've updated the ports database via csup within 24 hours of trying to compile mod_security2, so it isn't an outdated database. uname -a: FreeBSD Schiz0.securityexploits.com 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3#0: Sun Apr 15 23:22:36 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SCHIZ0NET i386 Thanks in advance! ~Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Install /ports/devel/pcre/ or apply the diff from Foxfair Hu ( http://www.freebsd.org/cgi/query-pr.cgi?pr=110645 ) The diff also includes the new version of mod_security2 (2.1.1) Benno ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: btx crashes when booting 6.1 from usb cdrom
Stephen Clark wrote: [...] If you could build custom boot images, try http://people.freebsd.org/~kib/realbtx realbtx.2.patch is the patch, and loader is the /boot/loader built with that patch applied. If you could rearrange CD image with that loader put into /boot, then try to load from it and report results. CAUTION: Do not install boot2 or loader on your harddrive, code had very little exposure and may cause you machine to become unbootable. Hi Konstantin, Thanks this worked. I have another question though. I mounted the distro 1 cd and cd to /cdrom and did tar cSf - . |(cd /usr/myboot;tar xSf -) so I could move in the new loader program. The problem is I ended up with an iso file system after I did mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /usr/myboot that was 991mb which was to big to put on a CD. Where did I go wrong? Since this was only a test I rm'ed packages, rescue and release directories, but how did it all fit on the CD originally? Many files are hardlinked on the original media (for example all in /rescue is hardlink to one binary), but tar makes a copy of each file. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
Kris Kennaway wrote: On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: Hi, Recently I have noticed that one of our Dell PE1950's has been crashing a lot with the following reason supervisor read, page not present. The system runs 6.2 Release under i386. I have attached 2 back traces, and I still have both cores if any more information is required. Any light that can be shed on this problem would be greatly appreciated. Tom === uname -a FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Apr 2 20:13:11 BST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE1950 i386 ## Core 1 [EMAIL PROTECTED] '13:14:47' '/home/london/tj' $ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1 [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: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x15c fault code = supervisor read, page not present instruction pointer = 0x20:0xc05df61f stack pointer = 0x28:0xe4f63c30 frame pointer = 0x28:0xe4f63c90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi1: net) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h25m33s Dumping 2047 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 7arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK) 7arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK) You might be hitting a bug in an obscure code path because of the above errors. I'm CC'ing someone who might be able to help. Kris Bear in mind that a recent urgent firmware update was released by Dell last week for 1950, 1955, and 2950 systems that is supposed to fix some data-corruption issues related to dual-core processors. I don't know if this problem is a symptom of that, but it strongly suggested to apply the firmware update regardless. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
On Mon, Apr 23, 2007 at 01:12:30PM -0400, Michael Proto wrote: Kris Kennaway wrote: On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: Hi, Recently I have noticed that one of our Dell PE1950's has been crashing a lot with the following reason supervisor read, page not present. The system runs 6.2 Release under i386. I have attached 2 back traces, and I still have both cores if any more information is required. Any light that can be shed on this problem would be greatly appreciated. Tom === uname -a FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Apr 2 20:13:11 BST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE1950 i386 ## Core 1 [EMAIL PROTECTED] '13:14:47' '/home/london/tj' $ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1 [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: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x15c fault code = supervisor read, page not present instruction pointer = 0x20:0xc05df61f stack pointer = 0x28:0xe4f63c30 frame pointer = 0x28:0xe4f63c90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi1: net) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h25m33s Dumping 2047 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 7arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK) 7arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK) You might be hitting a bug in an obscure code path because of the above errors. I'm CC'ing someone who might be able to help. Kris Bear in mind that a recent urgent firmware update was released by Dell last week for 1950, 1955, and 2950 systems that is supposed to fix some data-corruption issues related to dual-core processors. I don't know if this problem is a symptom of that, but it strongly suggested to apply the firmware update regardless. Thanks, this could be very relevant. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
Michael Proto wrote: Kris Kennaway wrote: On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: Hi, Recently I have noticed that one of our Dell PE1950's has been crashing a lot with the following reason supervisor read, page not present. The system runs 6.2 Release under i386. I have attached 2 back traces, and I still have both cores if any more information is required. Any light that can be shed on this problem would be greatly appreciated. SNIP/ You might be hitting a bug in an obscure code path because of the above errors. I'm CC'ing someone who might be able to help. Kris Bear in mind that a recent urgent firmware update was released by Dell last week for 1950, 1955, and 2950 systems that is supposed to fix some data-corruption issues related to dual-core processors. I don't know if this problem is a symptom of that, but it strongly suggested to apply the firmware update regardless. I have just been to dells site and there are firmware updates for almost every component in the system released about 2 weeks ago (10-11/4). I have around 17 [12]950's waiting to go into pre production testing at the moment so I think that I will spend some time upgrading the firmware on them now rather than later. Thanks for the heads up. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD DNS Resolver Issues?
OK, now I am a bit stumped, so wanted to post here in hopes someone might have an idea. First off the FBSD machine in question is an x86 server running 6.2-STABLE from a supped from a few weeks ago, so is fairly current. I use said machine to handle all of my eMail and things in general seem to work great, though I have this one mystery. I we try and send mail to [EMAIL PROTECTED] the mail will just set in the queue forever, until it's returned as a failure. Talking with the admins at wtplaw they are swearing their configs are correct, and it's something on our side. Looking at the mailq, I see: l3NEqolY01112428697 Mon Apr 23 10:52 [EMAIL PROTECTED] (Deferred: Name server: mail.wtplaw.com.: host name lookup fa) [EMAIL PROTECTED] So as it's quick an easy I used dig and did a lookup: $ host wtplaw.com wtplaw.com has address 69.20.43.246 wtplaw.com mail is handled by 10 mail.wtplaw.com. Then on mail.wtplaw.com: $ host mail.wtplaw.com mail.wtplaw.com has address 65.111.69.228 mail.wtplaw.com has address 66.166.181.163 Host mail.wtplaw.com not found: 2(SERVFAIL) ;; connection timed out; no servers could be reached As you can see I am getting a failure, which I know will make sendmail blow a gasket over the issue. Oh and use I have the WorkAroundBroken set in my configs. Here is where it gets interesting, and confuses me. I also have a Sun SPARC server running Solaris-10, so figured I would try the same on it. Note that both servers use the same DNS servers for resolution, plus I also tried the above specifying the actual listed nameservers for wtplaw.com and got the same results. OK, so let's try the above on my Solaris-10 server: $ host wtplaw.com wtplaw.com has address 69.20.43.246 wtplaw.com mail is handled by 10 mail.wtplaw.com. and: $ host mail.wtplaw.com mail.wtplaw.com has address 65.111.69.228 mail.wtplaw.com has address 66.166.181.163 Note I am getting no failure messages from my Solaris machine. So I even turned on -v verbose option. Here is from the FreeBSD machine: $ host -v mail.wtplaw.com Trying mail.wtplaw.com ;; -HEADER- opcode: QUERY, status: NOERROR, id: 27765 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;mail.wtplaw.com. IN A ;; ANSWER SECTION: mail.wtplaw.com.3 IN A 65.111.69.228 mail.wtplaw.com.3 IN A 66.166.181.163 ;; AUTHORITY SECTION: mail.wtplaw.com.85342 IN NS lp2.wtplaw.com. mail.wtplaw.com.85342 IN NS lp1.wtplaw.com. ;; ADDITIONAL SECTION: lp2.wtplaw.com. 85864 IN A 66.166.181.172 Received 117 bytes from 207.114.24.13#53 in 22 ms Trying mail.wtplaw.com Host mail.wtplaw.com not found: 2(SERVFAIL) Received 33 bytes from 207.114.24.13#53 in 80 ms Trying mail.wtplaw.com ;; connection timed out; no servers could be reached Note the failures. I am have to honestly say I am not totally sure what it's trying to do at the end there, maybe someone can explain that one to me. Here is the Solaris-10 machine making the same query: $ host -v mail.wtplaw.com Trying mail.wtplaw.com ;; -HEADER- opcode: QUERY, status: NOERROR, id: 549 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;mail.wtplaw.com. IN A ;; ANSWER SECTION: mail.wtplaw.com.3 IN A 65.111.69.228 mail.wtplaw.com.3 IN A 66.166.181.163 ;; AUTHORITY SECTION: mail.wtplaw.com.85225 IN NS lp1.wtplaw.com. mail.wtplaw.com.85225 IN NS lp2.wtplaw.com. ;; ADDITIONAL SECTION: lp2.wtplaw.com. 85747 IN A 66.166.181.172 Received 117 bytes from 207.114.24.13#53 in 40 ms Again, the query seemed fine, no troubles. As stated earlier, talking to the sysadmin of the wtplaw.com site, they are swearing there is nothing wrong, they are responding to queries as they should be, and that we have a configuration problem on our end. If this is true, I'd sure love to know what it is, so I can fix it, and if not I'd love to know what to tell them is wrong with their DNS so I can get it corrected. As right now I am bouncing mail from a few clients to this user, and I can't seem to find any resolution to this issue. When I realized that Solaris seems happy with their DNS, but FBSD is not, it just made this even more of a mystery. If anyone can help shed any light on this it would sure be appreciated.. --- -Howard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Compile Error: mod_security2
On 4/23/07, Benno [EMAIL PROTECTED] wrote: On 4/23/07, Schiz0 [EMAIL PROTECTED] wrote: Hey guys, Running 6.2-RELEASE-p3 and apache2.2.4. I'm trying to install mod_security2 from ports, and I'm getting the following error during the build http://Schiz0.securityexploits.com/mod_security2.ports.compile.error I've updated the ports database via csup within 24 hours of trying to compile mod_security2, so it isn't an outdated database. uname -a: FreeBSD Schiz0.securityexploits.com 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3#0: Sun Apr 15 23:22:36 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SCHIZ0NET i386 Thanks in advance! ~Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Install /ports/devel/pcre/ or apply the diff from Foxfair Hu ( http://www.freebsd.org/cgi/query-pr.cgi?pr=110645 ) The diff also includes the new version of mod_security2 (2.1.1) Benno Awesome, that patch did it. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
