6.3-BETA1: acpi_tz0: _TMP value is absurd, ignored (-13.4C)

2007-11-13 Thread Jan Henrik Sylvester
I upgraded an old machine from 6.2-RELEASE-p7 to 6.3-BETA1 (via freebsd-update). Now every ten seconds I get: acpi_tz0: _TMP value is absurd, ignored (-13.4C) At the same time, I have: hw.acpi.thermal.tz0.temperature: -273.2C The machine has a Gigabyte GA-686BX board with Intel 82440 BX

System unbootable after upgrade to FBSD 7

2007-11-13 Thread Gerrit Kühn
Hi, I just upgraded my first system from 6-stable to 7. installkernel and installworld went well. However, the system won't boot anymore. :-( The bootloader still appears, grabs kernel and modules, followed by Can't work out which disk we are booting from. Guessed BIOS device 0x not

Re: 7.0 beta2 vs. SATA DVD drive

2007-11-13 Thread Aryeh M. Friedman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Uwe Laverenz wrote: Hi, I was trying to install 7.0 beta 2 on a system that has a SATA attached DVD drive. The system starts to the point where it waits for the SCSI devices to initialize. After that it starts reading from the install media and

Re: 7.0 beta2 vs. SATA DVD drive

2007-11-13 Thread Uwe Laverenz
On Tue, Nov 13, 2007 at 07:04:34AM -0500, Aryeh M. Friedman wrote: and constantly gets read timeouts == no installation possible. Yes and it is under active investigation. Thank you. :) Uwe ___ freebsd-stable@freebsd.org mailing list

Re: System unbootable after upgrade to FBSD 7

2007-11-13 Thread Gerrit Kühn
On Tue, 13 Nov 2007 09:38:00 +0100 Gerrit Kühn [EMAIL PROTECTED] wrote about System unbootable after upgrade to FBSD 7: GK Can't work out which disk we are booting from. GK Guessed BIOS device 0x not found by probes, defaulting to GK disk0: GK panic: free: guard1 fail @ 0x6c23c GK from

Re: 7.0 beta2 vs. SATA DVD drive

2007-11-13 Thread Aryeh M. Friedman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Uwe Laverenz wrote: On Tue, Nov 13, 2007 at 07:04:34AM -0500, Aryeh M. Friedman wrote: and constantly gets read timeouts == no installation possible. Yes and it is under active investigation. Thank you. :) Just for the record what chipset is

Re: 7.0 beta2 vs. SATA DVD drive

2007-11-13 Thread Uwe Laverenz
On Tue, Nov 13, 2007 at 07:18:19AM -0500, Aryeh M. Friedman wrote: Just for the record what chipset is your Mobo (it has been reported on several but most commonly ICH9(R)? Also don't expect any more The board has an AMD 8151+8111 combo with a SiI 3114 SATA Controller, so it's not an Intel

reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Vivek Khera
I've got a Dell 1750 box that was rock-solid stable running 4.11 for a couple of years now operating a pretty busy website backend. A month or so ago we wiped it clean and repurposed it to run a different website running Drupal with a Varnish front-end cache using FreeBSD 6.2-RELEASE-p5.

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Vlad GALU
On 11/13/07, Vivek Khera [EMAIL PROTECTED] wrote: I've got a Dell 1750 box that was rock-solid stable running 4.11 for a couple of years now operating a pretty busy website backend. A month or so ago we wiped it clean and repurposed it to run a different website running Drupal with a Varnish

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Vivek Khera
On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote: vmio = 1 offset = Unhandled dwarf expression opcode 0x93 (kgdb) Do you happen to have ZERO_COPY_SOCKETS in your kernel config? Yes, I do. Are they known to be bad under certain loads or just in general. I don't have this

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Vlad GALU
On 11/13/07, Vivek Khera [EMAIL PROTECTED] wrote: On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote: vmio = 1 offset = Unhandled dwarf expression opcode 0x93 (kgdb) Do you happen to have ZERO_COPY_SOCKETS in your kernel config? Yes, I do. Are they known to be bad

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Kip Macy
Unfortunately, ZERO_COPY_SOCKETs have long been a known source of problems. I think also, when a page is copied as part of COW the new page is unwired (see pmap_copy et al.), this could lead to socow_iodone unwiring after send a page that was not wired. An added issue is that parts of the VM

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Vivek Khera
On Nov 13, 2007, at 5:13 PM, Kip Macy wrote: In the meantime, your best bet is to disable ZERO_COPY_SOCKETS. Thanks for the info. I'm putting the new kernel in place and will see what happens and report back. ___ freebsd-stable@freebsd.org

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Kris Kennaway
Kip Macy wrote: Unfortunately, ZERO_COPY_SOCKETs have long been a known source of problems. I think also, when a page is copied as part of COW the new page is unwired (see pmap_copy et al.), this could lead to socow_iodone unwiring after send a page that was not wired. An added issue is that

Re: reboot after panic: vm_page_unwire: invalid wire count: 0

2007-11-13 Thread Kip Macy
Various calls that downgrade permissions or virtually copy a pmap in pmap.c now remove PG_W (and did not 6 months ago). This may be the cause of the regression. It would probably be better (and faster) if the pages were held instead of wired. -Kip On Nov 13, 2007 4:49 PM, Kris Kennaway