Re: 6.2-STABLE deadlock?
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/ -- Adrian Wontroba ___ 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 ?
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. Ganbold Beni. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[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: Panic: vm_page_free: freeing wired page with 6.2 RELEASE
Hi, Can you post your kernel configuration file? It's the generic SMP kernel file (which includes GENERIC), with nothing changed. sysctl.conf is: kern.sugid_coredump=1 kern.timecounter.hardware=TSC kern.corefile=/var/core/%N-%P.core kern.maxfiles=64000 kern.maxfilesperproc=32000 The server has two CPUs. The only special thing is that with the current BIOS ACPI is broken. -- Martin FreeBSD 6.2-RELEASE #0: Tue Jan 23 11:13:16 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x641d> AMD Features=0x2000 Logical CPUs per core: 2 real memory = 3623665664 (3455 MB) avail memory = 3546501120 (3382 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic3: Assuming intbase of 72 ioapic4: Assuming intbase of 96 ioapic4 irqs 96-119 on motherboard ioapic3 irqs 72-95 on motherboard ioapic2 irqs 48-71 on motherboard ioapic1 irqs 24-47 on motherboard ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES cpu0 on motherboard cpu1 on motherboard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: vm_page_free: freeing wired page with 6.2 RELEASE
Martin Blapp wrote: Hi, Just got this panic on a loaded mailserver ... The server was rocking stable up to this panic, and after we loaded it a bit more recently, it paniced. Any ideas ? Can you post your kernel configuration file? Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic: vm_page_free: freeing wired page with 6.2 RELEASE
Hi,
Just got this panic on a loaded mailserver ... The server was rocking stable
up to this panic, and after we loaded it a bit more recently, it paniced.
Any ideas ?
--
Martin
#0 doadump () at pcpu.h:165
#1 0xc067550a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0675831 in panic (fmt=0xc0915bd0 "vm_page_free: freeing wired page") at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc07f15a3 in vm_page_free_toq (m=0xc25380b0) at
/usr/src/sys/vm/vm_page.c:1131
#4 0xc07f0ad1 in vm_page_free (m=0xc25380b0) at /usr/src/sys/vm/vm_page.c:471
#5 0xc07e4be0 in vm_fault (map=0xcadcf378, vaddr=678141952, fault_type=1
'\001', fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:632
#6 0xc088df07 in trap_pfault (frame=0xeb31f820, usermode=0, eva=678141952) at
/usr/src/sys/i386/i386/trap.c:722
#7 0xc088dc15 in trap (frame= {tf_fs = -1065549816, tf_es = -65496, tf_ds = -65496, tf_edi = -548069376,
tf_esi = 678141952, tf_ebp = -349046640, tf_isp = -349046708, tf_ebx = 16384,
tf_edx = 678158336, tf_ecx = 4096, tf_eax = -349045504, tf_trapno = 12, tf_err =
0, tf_eip = -1064779658, tf_cs = 32, tf_eflags = 66054, tf_esp = -349046248,
tf_ss = -349046324})at /usr/src/sys/i386/i386/trap.c:435
#8 0xc0879d4a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#9 0xc088c076 in slow_copyin () at /usr/src/sys/i386/i386/support.s:872
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP:
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PAE does not give any ram increase, why?
Artem Kuchin wrote: the number do not change with or without PAE Maybe i look in the wrong place? I'm not going to waste my time explaining for the hundredth time how the x86 memory layout works. If you want to recover the missing 256MB, go look in your BIOS for an option about memory hole remapping. No need, i know this stuff. Problem is that asus p5p800-vm bios does not have such option (no memory remapping support in chipset) , so, and simply assumed that in PAE mode this simply does not matter and it will give me whole 4GB. Isn't it so? Is it true for 64bit mode (amd64)? Please check the archives for my numerous discussions on how the memory layout works on x86. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PAE does not give any ram increase, why?
Artem Kuchin wrote: the number do not change with or without PAE No need, i know this stuff. Hmmm :-) Problem is that asus p5p800-vm bios does not have such option > (no memory remapping support in chipset) , so, and simply assumed that in PAE mode this simply does not matter and it will give me whole 4GB. Isn't it so? Is it true for 64bit mode (amd64)? That is a desktop board with an old desktop chipset, it will not remap anything over 4GB even if you are running 64-bit mode. It does most certainly not support PAE mode. Be happy that it is just 256MB memory that you can't use, it is not uncommon to loose up to 750MB! Best Regards, Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PAE does not give any ram increase, why?
On Sun, Apr 22, 2007 at 01:14:17PM +0400, Artem Kuchin wrote: > > >>the number do not change with or without PAE > >> > >>Maybe i look in the wrong place? > >> > > > >I'm not going to waste my time explaining for the hundredth time how > >the x86 memory layout works. If you want to recover the missing > >256MB, go look in your BIOS for an option about memory hole remapping. > > No need, i know this stuff. Problem is that asus p5p800-vm bios does not > have such option (no memory remapping support in chipset) > , so, and simply assumed that in PAE mode this simply > does not matter and it will give me whole 4GB. Isn't it so? > Is it true for 64bit mode (amd64)? It is not so for either of PAE or 64-bit mode. What those give you is the ability to address memory above the 4GB limit. In order to access memory below the 4GB boundary that is shadowed by various I/O-devices, the RAM will have to be remapped to somewehere else. So if you could remap the memory then PAE or 64-bit mode would give you the ability to access it. If you can't remap it you can't get hold of it. -- Erik Trulsson [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: PAE does not give any ram increase, why?
the number do not change with or without PAE Maybe i look in the wrong place? I'm not going to waste my time explaining for the hundredth time how the x86 memory layout works. If you want to recover the missing 256MB, go look in your BIOS for an option about memory hole remapping. No need, i know this stuff. Problem is that asus p5p800-vm bios does not have such option (no memory remapping support in chipset) , so, and simply assumed that in PAE mode this simply does not matter and it will give me whole 4GB. Isn't it so? Is it true for 64bit mode (amd64)? -- Regards, Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
Hi! > > ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, > default to deny, logging limited to 100 packets/entry by default > ad0: 114473MB at ata0-master UDMA100 > acd0: DVDR at ata1-master UDMA33 > ad4: 152627MB 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. >-p Drive of acd0: DVDR at ata1-master UDMA33 empty, there is not a disk. With kernel from the beginning of March and all was normal before. It is observed as on the branch of 6.2-STABLE so on CURRENT. # uname -a FreeBSD test.ua 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Apr 20 19:02:10 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAIL amd64 - vga0: 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 Waiting 5 seconds for SCSI devices to settle acd0: CDROM at ata0-master PIO4 afd0: 95MB at ata1-master PIO0 ad4: 76319MB at ata2-master SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 ??? afd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 ??? sa0 at ahc0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15)da0 at ata1 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a GEOM_ELI: Device ad4s1b.eli created. GEOM_ELI: Encryption: AES-CBC 256 GEOM_ELI: Crypto: software WARNING: /zip was not properly dismounted -- 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]"
