Re: FreeBSD Compiler Benchmark: gcc-base vs. gcc-ports vs. clang

Vinícius Zavam wrote: i'm still curious about things like CPUTYPE= and -march= configured as native, gentlemen. is it the golden egg to use with our system or not? why natives aren't in the benchs? /me feels confused. -- Vinícius Zavam profiles.google.com/egypcio Apparently

Re: FreeBSD Compiler Benchmark: gcc-base vs. gcc-ports vs. clang

On Sun, Mar 13, 2011 at 3:19 PM, Jakub Lach jakub_l...@mailplus.pl wrote: Vinícius Zavam wrote: i'm still curious about things like CPUTYPE= and -march= configured as native, gentlemen. is it the golden egg to use with our system or not? why natives aren't in the benchs? /me

`panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

This usually has to do with a hung SCSI command. That this is a notebook indicates to me that it's possibly a USB device. A boot -v with 8.2RELEASE and then a boot -v with this snapshot might tell us what's up. Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

On Mon, Mar 14, 2011 at 02:01:38AM +0300, Yuri Pankov wrote: Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... Not sure if these are useful: http://darklight.org.ru/misc/dv8.dmesg.boot http://darklight.org.ru/misc/dv8.pciconf Yuri

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... What are my options for saving the output from failed boot other than

[ath] AR9285/AR2427 users - please test -HEAD

Hi all, I've been working on AR9285 and AR2427 specific fixes. I seem to have fixed the issues I've seen with my AR9285 and AR2427 (and my AR2427 actually performs better under FreeBSD than Linux. Hah!) Just to be clear - the AR2427 support now seems to work and be stable. I'm seeing 24mbit in

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

On 3/13/2011 5:03 PM, Yuri Pankov wrote: On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... What are my options for saving

[head tinderbox] failure on ia64/ia64

TB --- 2011-03-14 02:05:46 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-14 02:05:46 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-03-14 02:05:46 - cleaning the object tree TB --- 2011-03-14 02:05:57 - cvsupping the source tree TB --- 2011-03-14 02:05:57 -

[head tinderbox] failure on powerpc/powerpc

TB --- 2011-03-14 03:42:31 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-14 03:42:31 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2011-03-14 03:42:31 - cleaning the object tree TB --- 2011-03-14 03:42:45 - cvsupping the source tree TB --- 2011-03-14 03:42:45 -