From rjb at robertjbrown.com  Mon Dec  1 00:40:03 2008
From: rjb at robertjbrown.com (Robert J. Brown)
Date: Mon Dec  1 04:24:43 2008
Subject: amd64/129315: amd64 motherboard: Intel DG965WH motherboard
	compatibility with AMD64
Message-ID: <200812010840.mB18e30K037818@freefall.freebsd.org>

The following reply was made to PR amd64/129315; it has been noted by GNATS.

From: "Robert J. Brown" <rjb@robertjbrown.com>
To: bug-followup@FreeBSD.org,
 rjb@robertjbrown.com
Cc:  
Subject: Re: amd64/129315: amd64 motherboard: Intel DG965WH motherboard compatibility with AMD64
Date: Mon, 1 Dec 2008 00:33:57 -0800

 I have since tried a few things:
 
 -- Removed memory down to 1GB (matched pair of 512mb modules, dual  
 channel mode - channel A DIMM0, channel B DIMM0)
 
 -- Backed the BIOS down to earlier revisions due to other reports of  
 bug issues with newer BIOSes. I tried 1754, 1716, 1705, 1699, and  
 1669. The 1669 BIOS was supposed to fix some bugs introduced in later  
 revisions but my system behaves exactly the same. 
 
 
 With 7.0-RELEASE, option 1 on the install CD still does a clean reboot  
 about half way through kernel initialization. Option 2 to disable ACPI  
 gets further and then hangs while trying to mount root from ufs:/dev/ 
 md0. This requires a manual reboot.
 
 Here is what I can see of the screen as it is frozen from option #2.  
 This was manually typed in.
 
 -- BEGIN SCREEN CAPTURE --
 
 device_attach: atapci1 attach returned 6
 pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
 orm0: <ISA Option ROMs> at iomem 0xcb800-0xcd7ff, 0xcd800-0xce7ff,  
 0xce800-0xcf7ff on isa0
 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 fdc0: cannot reserve interrupt line
 ppc0: cannot reserve I/O port range
 sc0: <System console> at flags 0x100 on isa0
 sc0: VGA <16 virtual consoles, flags=0x300>
 sio0: configured irq4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0: configured irq4 not in bitmap of probed irqs 0
 sio0: port may not be enabled
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1: configured irq 3 not in bitmap of probed irqs 0
 sio1: port may not be enabled
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on  
 isa0
 RTC BIOS diagnostic error 80<clock_battery>
 Timecounter "TSC" frequency 1872271506 Hz quality 800
 Timecounters ticket every 1.000 msec
 hptrr: no controller detected
 md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xffffffff80bc6c08
 Trying to mount root from ufs:/dev/md0
 
 -- END SCREEN CAPTURE --
 
 
 My next step is to re-roll the latest CVSUP'd sources from the 7.1  
 tree into a make release on a different (working) amd64 system. I'd  
 like to see what the latest source will get me but I'm not optimistic  
 at this point.
 
 Question: should I try the i386 build to see if there are any  
 differences? I really need to run amd64 but I am open to trying i386  
 if it would help get to the bottom of this.
From bugmaster at FreeBSD.org  Mon Dec  1 03:06:51 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Dec  1 04:25:00 2008
Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org
Message-ID: <200812011106.mB1B6pCh052468@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/129315 amd64      amd64 motherboard: Intel DG965WH motherboard compatibi
o amd64/129238 amd64      [panic] System randomly panics
f amd64/128978 amd64      [install] FreeBSD 6.3 64-bit  panics at boot time duri
o amd64/128810 amd64      AMD 64 port installation
o amd64/128765 amd64      [install] Install CD loads to Install choices but stop
o amd64/128686 amd64      [ata] can't detect SATA Disk on 8.0-Current with NF550
o amd64/128524 amd64      No geom documentation for loading gjournal
o amd64/128263 amd64      [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a
o amd64/128259 amd64      csh(1): "`" crashes csh
o amd64/128236 amd64      portsdb -Uu Indexing error
f kern/128102  amd64      AsusRock 939N68PV-GLAN not recognized
o amd64/127787 amd64      [lor] 3 lock LOR in recent CURRENT
o amd64/127640 amd64      GCC will not build shared libraries with -fprofile-gen
o amd64/127492 amd64      [zfs] System hang on ZFS input-output
o amd64/127484 amd64      [timecounters] Drift problem with FreeBSD 7.0 and 7.1 
o amd64/127451 amd64      [scheduler] incorrect load on quad core
o amd64/127397 amd64      [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI
s amd64/127276 amd64      ldd(1) invokes linux yes
o amd64/127129 amd64      mdconfig(8) is core dumping with Segmentation Fault 11
f amd64/125943 amd64      Serial Consoles do not work on amd64 freebsd
o amd64/125873 amd64      [smbd] [panic] Repeated kernel panics, trap 12 page fa
o amd64/125002 amd64      [install] amd64, SATA hard disks not detected
o amd64/124432 amd64      [panic] 7.0-STABLE panic: invalbuf: dirty bufs
o amd64/124134 amd64      [kernel] The kernel doesn't follow the calling convent
o amd64/123562 amd64      [install] FreeBSD amd64 not installs
o amd64/123520 amd64      [ahd] unable to boot from net while using ahd
o amd64/123456 amd64      fstat(1): /usr/bin/fstat shows error messages and hang
f amd64/123275 amd64      [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re
o kern/122782  amd64      [modules] accf_http.ko kernel module is not loadable
o amd64/122695 amd64      [cpufreq] Lack of cpufreq control using amd64 eith cor
o amd64/122624 amd64      unusable minimal installation of FreeBSD-7.0
o amd64/122549 amd64      7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial 
o amd64/122468 amd64      Compile problems after upgrading to 7.0
o amd64/122174 amd64      [panic] 7.0 no longer includes "device atpic" so fails
o amd64/121590 amd64      [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet
o amd64/121439 amd64      [boot] Installation of FreeBSD 7.0 fails: ACPI problem
o amd64/120202 amd64      [amd64] [patch] [panic] kernel panic at start_all_aps,
o amd64/119936 amd64      [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis
o amd64/119591 amd64      [amd64] [patch] time_t on 64-bit architecture
o amd64/117418 amd64      [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh
o amd64/117316 amd64      [acpi] ACPI lockups on SuperMicro motherboard
o amd64/117296 amd64      [ata] I don`t see second SATA IDE on VIA VT8237A
a amd64/117186 amd64      [modules] kldload Unsupported file type on STABLE amd6
s amd64/116689 amd64      [request] support for MSI K9MM-V
f amd64/116670 amd64      [ata] onboard SATA RAID1 controllers not supported for
o amd64/116620 amd64      [hang] ifconfig spins when creating carp(4) device on 
f amd64/116457 amd64      [install] can't install freebsd on dv9420us
o amd64/116322 amd64      [panic] At start fsck on current, the system panics
o amd64/116159 amd64      [panic] Panic while debugging on CURRENT
s amd64/115815 amd64      [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp
o amd64/115581 amd64      [Makefile] [patch] -mfancy-math-387 has no effect
o amd64/115194 amd64      LCD screen remains blank after Dell XPS M1210 lid is c
o amd64/114270 amd64      [cpufreq] cpufreq doesnt work when compiled in to kern
o amd64/114111 amd64      [nfs] System crashes while writing on NFS-mounted shar
f amd64/113021 amd64      [re] ASUS M2A-VM onboard NIC does not work
o amd64/112222 amd64      [libc] 32-bit libc incorrectly converts some FP number
f amd64/111992 amd64      [boot] BTX failed - HP Laptop dv2315nr
o amd64/110655 amd64      [threads] 32 bit threaded applications crash on amd64 
o amd64/110599 amd64      [geli] geli attach to gmirror device hangs and cannot 
s amd64/108861 amd64      [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work
o amd64/106186 amd64      [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p
f amd64/105629 amd64      [re] TrendNet TEG-BUSR 10/100/1000 disables itself on 
f amd64/105531 amd64      [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does
f amd64/105514 amd64      [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv
o amd64/102716 amd64      ex with no argument in an xterm gets SIGSEGV
o amd64/97337  amd64      [dri] xorg reboots system if dri module is enabled
o amd64/95888  amd64      [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP 
f amd64/94989  amd64      [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64)
o amd64/94677  amd64      [panic] panic in amd64 install at non-root user creati
o amd64/93961  amd64      [busdma] Problem in bounce buffer handling in sys/amd6
o amd64/92337  amd64      [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff
f amd64/91492  amd64      [boot] BTX halted
o amd64/91405  amd64      [asr] [panic] Kernel panic caused by asr on 6.0-amd64 
o amd64/89501  amd64      [install] System crashes on install using ftp on local
o amd64/88790  amd64      [panic] kernel panic on first boot (after the FreeBSD 
o amd64/88568  amd64      [panic] 6.0-RELEASE install cd does not boot with usb 
o amd64/87689  amd64      [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE
o amd64/87316  amd64      [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6
o amd64/87305  amd64      [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in
f amd64/87258  amd64      [smp] [boot] cannot boot with SMP and Areca ARC-1160 r
f amd64/86080  amd64      [radeon] [hang] radeon DRI causes system hang on amd64
s amd64/85273  amd64      [install] FreeBSD (NetBSD or OpenBSD) not install on l
o amd64/78406  amd64      [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys
o amd64/76136  amd64      [hang] system halts before reboot
o amd64/74747  amd64      [panic] System panic on shutdown when process will not
o amd64/73322  amd64      [msdosfs] [hang] unarchiving /etc to msdosfs locks up 

86 problems total.

From mav at FreeBSD.org  Mon Dec  1 09:19:36 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Mon Dec  1 09:19:49 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <20081201150743.V34249@sola.nimnet.asn.au>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <49334110.4010308@FreeBSD.org>
	<20081201150743.V34249@sola.nimnet.asn.au>
Message-ID: <49341CA4.8060801@FreeBSD.org>

Ian Smith wrote:
> On Mon, 1 Dec 2008, Alexander Motin wrote:
>  > Alexander Motin wrote:
>  > > As result, I have found, that if I am inserting:
>  > > qqq:
>  > >         jmp     qqq
>  > > lines before line 98 of acpi_switch.S:
>  > >     movl    $MSR_MTRRdefType, %ecx
>  > >         movl    WAKEUP_CTX(mtrr), %eax
>  > >         wrmsr
>  > > system hangs, but if I insert it just after them - system reboots.
>  > > 
>  > > With just commenting this three lines I was able to get successful
>  > > suspend/resume with UP amd64 kernel!!!
>  > > 
>  > > Here is problems I still have now:
>  > >  - SMP kernel resume is not working, system reboots while doing
>  > > acpi_wakeup_cpus();
>  > >  - SATA controller does not resumes correctly, it dies for some reason,
>  > > reporting timeouts on any request;
>  > 
>  > This one is not a problem anymore. Seems to be fixed.
> 
> Progress!
> 
>  > >  - text mode video does not restores on resume, while Xorg graphic one
>  > > does. hw.acpi.reset_video=1 does not help, it just hanging resume process.
> 
> Longshot: hw.syscons.sc_no_suspend_vtswitch=1 fixes similar symptoms on 
> two (older, i386 and UP) laptops here.  Some folks have reported needing 
> to have VESA loaded to get text mode video back up.  Maybe worth a try?

vtswitch does not help and vesa generally does not working under amd64.

-- 
Alexander Motin
From tinderbox at freebsd.org  Tue Dec  2 02:16:43 2008
From: tinderbox at freebsd.org (FreeBSD Tinderbox)
Date: Tue Dec  2 02:16:50 2008
Subject: [head tinderbox] failure on amd64/amd64
Message-ID: <20081202101639.93F7773039@freebsd-current.sentex.ca>

TB --- 2008-12-02 09:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2008-12-02 09:00:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2008-12-02 09:00:00 - cleaning the object tree
TB --- 2008-12-02 09:00:53 - cvsupping the source tree
TB --- 2008-12-02 09:00:53 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2008-12-02 09:01:00 - building world
TB --- 2008-12-02 09:01:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-02 09:01:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-02 09:01:00 - TARGET=amd64
TB --- 2008-12-02 09:01:00 - TARGET_ARCH=amd64
TB --- 2008-12-02 09:01:00 - TZ=UTC
TB --- 2008-12-02 09:01:00 - __MAKE_CONF=/dev/null
TB --- 2008-12-02 09:01:00 - cd /src
TB --- 2008-12-02 09:01:00 - /usr/bin/make -B buildworld
>>> World build started on Tue Dec  2 09:01:02 UTC 2008
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
[...]
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_args.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_basic.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_bin.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_cred.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_files.c
cc1: warnings being treated as errors
/src/usr.bin/procstat/procstat_files.c: In function 'procstat_files':
/src/usr.bin/procstat/procstat_files.c:272: warning: comparison between signed and unsigned
*** Error code 1

Stop in /src/usr.bin/procstat.
*** Error code 1

Stop in /src/usr.bin.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-12-02 10:16:39 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-12-02 10:16:39 - ERROR: failed to build world
TB --- 2008-12-02 10:16:39 - 3596.12 user 362.23 system 4598.56 real


http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full
From alias at jurrie.net  Tue Dec  2 01:20:03 2008
From: alias at jurrie.net (Jurriaan Nijkamp)
Date: Tue Dec  2 04:25:34 2008
Subject: amd64/129238: [panic] System randomly panics
Message-ID: <200812020920.mB29K3ox098098@freefall.freebsd.org>

The following reply was made to PR amd64/129238; it has been noted by GNATS.

From: "Jurriaan Nijkamp" <alias@jurrie.net>
To: bug-followup@FreeBSD.org,
 alias@jurrie.net
Cc:  
Subject: Re: amd64/129238: [panic] System randomly panics
Date: Tue, 2 Dec 2008 08:13:22 +0100 (CET)

 After another crash yesterday, I got a new dump which, according to
 someone who knows what he's talking about, is actually useful. He also
 said the problem may lie with faulty memory, but I must say I did a
 memtest86+ test last week which said my memory was working perfectly.
 
 I am pasting the output of kgdb below.
 
 ---- output of kgdb kernel.debug /var/crash/vmcore.9 ----
 
 [GDB will not be able to debug user-mode threads:
 /usr/lib/libthread_db.so: Unde                                 fined
 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 "amd64-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   = 0xffff800004003908
 fault code              = supervisor read data, page not present
 instruction pointer     = 0x8:0xffffffff8072436c
 stack pointer           = 0x10:0xffffffffae6d2a00
 frame pointer           = 0x10:0x4000000000
 code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags        = interrupt enabled, resume, IOPL = 0
 current process         = 5551 (sed)
 trap number             = 12
 panic: page fault
 cpuid = 0
 Uptime: 4h42m45s
 Physical memory: 2035 MB
 Dumping 311 MB: 296 280 264 248 232 216 200 184 168 152 136 120 104 88 72
 56 40                                  24 8
 
 #0  doadump () at pcpu.h:194
 194             __asm __volatile("movq %%gs:0,%0" : "=r" (td));
 (kgdb) bt
 #0  doadump () at pcpu.h:194
 #1  0x0000000000000004 in ?? ()
 #2  0xffffffff804776c9 in boot (howto=260)
     at /usr/src/sys/kern/kern_shutdown.c:409
 #3  0xffffffff80477acd in panic (fmt=0x104 <Address 0x104 out of bounds>)
     at /usr/src/sys/kern/kern_shutdown.c:563
 #4  0xffffffff8072edd4 in trap_fatal (frame=0xffffff00018bc9c0,
     eva=18446742974225594576) at /usr/src/sys/amd64/amd64/trap.c:724
 #5  0xffffffff8072f1a5 in trap_pfault (frame=0xffffffffae6d2950, usermode=0)
     at /usr/src/sys/amd64/amd64/trap.c:641
 #6  0xffffffff8072fae8 in trap (frame=0xffffffffae6d2950)
     at /usr/src/sys/amd64/amd64/trap.c:410
 #7  0xffffffff8071575e in calltrap ()
     at /usr/src/sys/amd64/amd64/exception.S:169
 #8  0xffffffff8072436c in pmap_remove_pages (pmap=0xffffff0001ab7778)
     at /usr/src/sys/amd64/amd64/pmap.c:388
 #9  0xffffffff80688238 in vmspace_exit (td=0xffffff00018bc9c0)
     at /usr/src/sys/vm/vm_map.c:404
 #10 0xffffffff804577ac in exit1 (td=0xffffff00018bc9c0, rv=0)
     at /usr/src/sys/kern/kern_exit.c:294
 #11 0xffffffff80458b5e in sys_exit (td=Variable "td" is not available.
 ) at /usr/src/sys/kern/kern_exit.c:98
 #12 0xffffffff8072f427 in syscall (frame=0xffffffffae6d2c70)
     at /usr/src/sys/amd64/amd64/trap.c:852
 #13 0xffffffff8071596b in Xfast_syscall ()
     at /usr/src/sys/amd64/amd64/exception.S:290
 #14 0x00000008006a8b3c in ?? ()
 Previous frame inner to this frame (corrupt stack?)
 
 ---- end kgdb output ----
 
 After this, following instructions given to me, I jumped to step #8 and
 did a 'list' command:
 
 ---- followup output ----
 
 (kgdb) frame 8
 #8  0xffffffff8072436c in pmap_remove_pages (pmap=0xffffff0001ab7778)
     at /usr/src/sys/amd64/amd64/pmap.c:388
 388             return (PTmap + ((va >> PAGE_SHIFT) & mask));
 (kgdb) list
 383     PMAP_INLINE pt_entry_t *
 384     vtopte(vm_offset_t va)
 385     {
 386             u_int64_t mask = ((1ul << (NPTEPGSHIFT + NPDEPGSHIFT +
 NPDPEPGSHIFT + NPML4EPGSHIFT)) - 1);
 387
 388             return (PTmap + ((va >> PAGE_SHIFT) & mask));
 389     }
 390
 391     static __inline pd_entry_t *
 392     vtopde(vm_offset_t va)
 
 ---- end followup output ----
 
From gavin at FreeBSD.org  Tue Dec  2 06:06:03 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Tue Dec  2 06:06:09 2008
Subject: amd64/116457: [install] can't install freebsd on dv9420us
Message-ID: <200812021406.mB2E62QK018441@freefall.freebsd.org>

Synopsis: [install] can't install freebsd on dv9420us

State-Changed-From-To: feedback->closed
State-Changed-By: gavin
State-Changed-When: Tue Dec 2 14:04:12 UTC 2008
State-Changed-Why: 
Feedback timeout (6 months).  I suspect this may be fixed with the BTX
changes in 7.1 / 6.4.  To submitter: if you do still see this problem
with 7.1 let us know and we can reopen the PR.


Responsible-Changed-From-To: freebsd-amd64->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Tue Dec 2 14:04:12 UTC 2008
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=116457
From hk at alogis.com  Tue Dec  2 06:27:46 2008
From: hk at alogis.com (Holger Kipp)
Date: Tue Dec  2 06:28:41 2008
Subject: amd64/129238: [panic] System randomly panics
In-Reply-To: <200812020920.mB29K3ox098098@freefall.freebsd.org>
References: <200812020920.mB29K3ox098098@freefall.freebsd.org>
Message-ID: <20081202141302.GA2745@intserv.int1.b.intern>

On Tue, Dec 02, 2008 at 09:20:03AM +0000, Jurriaan Nijkamp wrote:
> The following reply was made to PR amd64/129238; it has been noted by GNATS.
> 
> From: "Jurriaan Nijkamp" <alias@jurrie.net>
> To: bug-followup@FreeBSD.org,
>  alias@jurrie.net
> Cc:  
> Subject: Re: amd64/129238: [panic] System randomly panics
> Date: Tue, 2 Dec 2008 08:13:22 +0100 (CET)
> 
>  After another crash yesterday, I got a new dump which, according to
>  someone who knows what he's talking about, is actually useful. He also
>  said the problem may lie with faulty memory, but I must say I did a
>  memtest86+ test last week which said my memory was working perfectly.

I once had a board (high quality) with memory (high quality) with 
memory problems - ie a simple make -j8 buildworld would reliably panic
the system, but running memtest for hours did not show any problems.

It turned out to be a timing issue - we did hit exactly the combination
of memory and mainboard that didn't work well together. We swapped memory
with a different system and both were running fine afterwards.

So please do not rely on output of memtest alone - it is not stressing 
the system the way real applications do.

>  I am pasting the output of kgdb below.

Can't comment on kgdb-output. Sorry.

Regards,
Hoger Kipp
From tinderbox at freebsd.org  Tue Dec  2 07:17:47 2008
From: tinderbox at freebsd.org (FreeBSD Tinderbox)
Date: Tue Dec  2 07:17:54 2008
Subject: [head tinderbox] failure on amd64/amd64
Message-ID: <20081202151745.1627A73039@freebsd-current.sentex.ca>

TB --- 2008-12-02 14:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2008-12-02 14:00:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2008-12-02 14:00:00 - cleaning the object tree
TB --- 2008-12-02 14:00:24 - cvsupping the source tree
TB --- 2008-12-02 14:00:24 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2008-12-02 14:00:32 - building world
TB --- 2008-12-02 14:00:32 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-02 14:00:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-02 14:00:32 - TARGET=amd64
TB --- 2008-12-02 14:00:32 - TARGET_ARCH=amd64
TB --- 2008-12-02 14:00:32 - TZ=UTC
TB --- 2008-12-02 14:00:32 - __MAKE_CONF=/dev/null
TB --- 2008-12-02 14:00:32 - cd /src
TB --- 2008-12-02 14:00:32 - /usr/bin/make -B buildworld
>>> World build started on Tue Dec  2 14:00:35 UTC 2008
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
[...]
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_files.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_kstack.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_threads.c
cc -O2 -pipe  -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wno-uninitialized -Wno-pointer-sign -c /src/usr.bin/procstat/procstat_vm.c
cc1: warnings being treated as errors
/src/usr.bin/procstat/procstat_vm.c: In function 'procstat_vm':
/src/usr.bin/procstat/procstat_vm.c:59: warning: format '%*p' expects type 'void *', but argument 3 has type 'uint64_t'
/src/usr.bin/procstat/procstat_vm.c:60: warning: format '%*p' expects type 'void *', but argument 3 has type 'uint64_t'
*** Error code 1

Stop in /src/usr.bin/procstat.
*** Error code 1

Stop in /src/usr.bin.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-12-02 15:17:45 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-12-02 15:17:45 - ERROR: failed to build world
TB --- 2008-12-02 15:17:45 - 3597.14 user 359.62 system 4664.35 real


http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full
From jkim at FreeBSD.org  Tue Dec  2 09:43:30 2008
From: jkim at FreeBSD.org (Jung-uk Kim)
Date: Tue Dec  2 09:43:42 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4932F34C.1040804@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org>
Message-ID: <200812021243.08513.jkim@FreeBSD.org>

On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote:
> Hi.
>
> Alexander Motin wrote:
> > Jung-uk Kim wrote:
> >> I was working on suspend/resume support for amd64 and this is
> >> the result.  It works with a modified QEMU (QEMU does not
> >> support S3) but real boxes that I have don't seem to like it
> >> (e.g., broken BIOSes). If there is someone interested in
> >> finishing it off or giving it a try, the patch is here:
> >>
> >> http://people.freebsd.org/~jkim/amd64_suspend.diff
> >
> > I have tried it on my Acer TM6292. S1/S2 are unsupported. On S3
> > system successfully got down, but on wakeup button, two seconds
> > after power up, even without video initialization, it shut down,
> > reset and then started usual boot. I have tried both original and
> > updated BIOS, without any difference.
> >
> > Can I give you any other help?
>
> I have spent a day investigating the problem. I was inserting empty
> infinite loop into the different points of wakeup process trying to
> find the place where system reboots. I just haven't found any other
> feedback channel as video is not initialized and beeper is not
> working for some reason.
>
> As result, I have found, that if I am inserting:
> qqq:
>
>          jmp     qqq
> lines before line 98 of acpi_switch.S:
> 	movl    $MSR_MTRRdefType, %ecx
>
>          movl    WAKEUP_CTX(mtrr), %eax
>
>          wrmsr
> system hangs, but if I insert it just after them - system reboots.
>
> With just commenting this three lines I was able to get successful
> suspend/resume with UP amd64 kernel!!!

Good catch!  I can confirm this is a correct bandaid.  We cannot 
restore this MSR without restoring entire MTRR map.  Actually, I 
should have written separate functions to save/restore all global 
MSRs.  Only per-CPU MSRs should be embedded like that.

> Here is problems I still have now:
>   - SMP kernel resume is not working, system reboots while doing
> acpi_wakeup_cpus();

My dual-core CPU seems to resume okay but quite unstable.  Can you try 
something like the following in amd64/mp_machdep.c and tell me if it 
helps?

------------
@@ -57,6 +57,7 @@
 #include <vm/vm_extern.h>

 #include <machine/apicreg.h>
+#include <machine/cpufunc.h>
 #include <machine/md_var.h>
 #include <machine/mp_watchdog.h>
 #include <machine/pcb.h>
@@ -1121,6 +1121,8 @@
	int cpumask = PCPU_GET(cpumask);
 
	if (savectx2(&stopxpcbs[cpu])) {
+		/* Flush CPU cache. */
+		wbinvd();
		/* Indicate that we are suspended. */
		atomic_set_int(&stopped_cpus, cpumask);
	} else {
------------

>   - text mode video does not restores on resume, while Xorg graphic
> one does. hw.acpi.reset_video=1 does not help, it just hanging
> resume process.

It is very common problem for modern video cards.  We cannot do much 
here without help of GPU-specific routines (e.g., ATI ATOM BIOS 
parser for RadeonHD) or in-kernel realmode emulation[1] (e.g., 
NetBSD).

Thanks for the feedback!

Jung-uk Kim

[1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c
From mav at FreeBSD.org  Tue Dec  2 11:03:51 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Tue Dec  2 11:03:58 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <200812021243.08513.jkim@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org>
	<200812021243.08513.jkim@FreeBSD.org>
Message-ID: <49358684.7010508@FreeBSD.org>

Hi.

Jung-uk Kim wrote:
>> Here is problems I still have now:
>>   - SMP kernel resume is not working, system reboots while doing
>> acpi_wakeup_cpus();
> 
> My dual-core CPU seems to resume okay but quite unstable.  Can you try 
> something like the following in amd64/mp_machdep.c and tell me if it 
> helps?
> 
> ------------
> @@ -57,6 +57,7 @@
>  #include <vm/vm_extern.h>
> 
>  #include <machine/apicreg.h>
> +#include <machine/cpufunc.h>
>  #include <machine/md_var.h>
>  #include <machine/mp_watchdog.h>
>  #include <machine/pcb.h>
> @@ -1121,6 +1121,8 @@
> 	int cpumask = PCPU_GET(cpumask);
>  
> 	if (savectx2(&stopxpcbs[cpu])) {
> +		/* Flush CPU cache. */
> +		wbinvd();
> 		/* Indicate that we are suspended. */
> 		atomic_set_int(&stopped_cpus, cpumask);
> 	} else {
> ------------

Wow, it works!

I am writing this letter just after suspending/resuming my dual-core C2D 
system 4 times straight. Music plays, USB, SATA, all other hardware 
works fine. What kind of instability do you have?

The only strange effect I have noticed was incorrect CPU time some 
processes got:
%ps ax
   PID  TT  STAT      TIME COMMAND
    12  ??  WL   280503:38,05 [intr]
  1430  ??  Ss   280503:38,34 icewm

But I think it is more timer driver related then resume itself.

> Thanks for the feedback!

Many thanks to you! I hope this long-waited feature will be finished!

-- 
Alexander Motin
From mav at FreeBSD.org  Tue Dec  2 11:26:56 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Tue Dec  2 11:27:02 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49358A3F.7020701@root.org>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>	<4932F34C.1040804@FreeBSD.org>	<200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org>
Message-ID: <49358BED.3030903@FreeBSD.org>

Nate Lawson wrote:
>> The only strange effect I have noticed was incorrect CPU time some
>> processes got:
>> %ps ax
>>   PID  TT  STAT      TIME COMMAND
>>    12  ??  WL   280503:38,05 [intr]
>>  1430  ??  Ss   280503:38,34 icewm
>>
>> But I think it is more timer driver related then resume itself.
> 
> If you are using the LAPIC timer (default), it won't be running properly
> during resume.  However, this wide discrepancy seems to indicate that
> the timer state is not being resumed properly.  What if you use the ACPI
> timer (hw.timecounter.* I think are the sysctls)?

As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast 
as time source and TSC as kernel DELAY() source.

%sysctl -a | grep timecounter
kern.timecounter.tick: 1
kern.timecounter.choice: TSC(-100) ACPI-fast(1000) HPET(900) i8254(0) 
dummy(-1000000)
kern.timecounter.hardware: ACPI-fast
kern.timecounter.nsetclock: 3
kern.timecounter.ngetmicrotime: 353840
kern.timecounter.ngetnanotime: 481
kern.timecounter.ngetbintime: 0
kern.timecounter.ngetmicrouptime: 2014472
kern.timecounter.ngetnanouptime: 8950060
kern.timecounter.ngetbinuptime: 419099
kern.timecounter.nmicrotime: 1460084
kern.timecounter.nnanotime: 40830
kern.timecounter.nbintime: 1500942
kern.timecounter.nmicrouptime: 2210
kern.timecounter.nnanouptime: 21
kern.timecounter.nbinuptime: 1988392
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.i8254.counter: 46767
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.HPET.counter: 3274417396
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.quality: 900
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.ACPI-fast.counter: 14616414
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.quality: 1000
kern.timecounter.tc.TSC.mask: 4294967295
kern.timecounter.tc.TSC.counter: 3757339660
kern.timecounter.tc.TSC.frequency: 2394021468
kern.timecounter.tc.TSC.quality: -100
kern.timecounter.smp_tsc: 0
kern.timecounter.invariant_tsc: 1

There is sure some problem with LAPIC:
%vmstat -i
interrupt                          total       rate
.....
irq257: bge0                       70774         29
cpu1: timer                        17600          7
cpu1: timer                        27617         11
cpu1: timer                        15849          6
cpu1: timer                        15413          6
cpu1: timer                       877180        367
Total                            2284801        957

-- 
Alexander Motin
From nate at root.org  Tue Dec  2 11:31:53 2008
From: nate at root.org (Nate Lawson)
Date: Tue Dec  2 11:38:14 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49358684.7010508@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>	<4932F34C.1040804@FreeBSD.org>	<200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org>
Message-ID: <49358A3F.7020701@root.org>

Alexander Motin wrote:
> Hi.
> 
> Jung-uk Kim wrote:
>>> Here is problems I still have now:
>>>   - SMP kernel resume is not working, system reboots while doing
>>> acpi_wakeup_cpus();
>>
>> My dual-core CPU seems to resume okay but quite unstable.  Can you try
>> something like the following in amd64/mp_machdep.c and tell me if it
>> helps?
>>
>> ------------
>> @@ -57,6 +57,7 @@
>>  #include <vm/vm_extern.h>
>>
>>  #include <machine/apicreg.h>
>> +#include <machine/cpufunc.h>
>>  #include <machine/md_var.h>
>>  #include <machine/mp_watchdog.h>
>>  #include <machine/pcb.h>
>> @@ -1121,6 +1121,8 @@
>>     int cpumask = PCPU_GET(cpumask);
>>  
>>     if (savectx2(&stopxpcbs[cpu])) {
>> +        /* Flush CPU cache. */
>> +        wbinvd();
>>         /* Indicate that we are suspended. */
>>         atomic_set_int(&stopped_cpus, cpumask);
>>     } else {
>> ------------
> 
> Wow, it works!
> 
> I am writing this letter just after suspending/resuming my dual-core C2D
> system 4 times straight. Music plays, USB, SATA, all other hardware
> works fine. What kind of instability do you have?

Thank you both for debugging this.  It's good to see progress on
suspend/resume.

> The only strange effect I have noticed was incorrect CPU time some
> processes got:
> %ps ax
>   PID  TT  STAT      TIME COMMAND
>    12  ??  WL   280503:38,05 [intr]
>  1430  ??  Ss   280503:38,34 icewm
> 
> But I think it is more timer driver related then resume itself.

If you are using the LAPIC timer (default), it won't be running properly
during resume.  However, this wide discrepancy seems to indicate that
the timer state is not being resumed properly.  What if you use the ACPI
timer (hw.timecounter.* I think are the sysctls)?

-- 
Nate
From jhb at freebsd.org  Tue Dec  2 13:15:14 2008
From: jhb at freebsd.org (John Baldwin)
Date: Tue Dec  2 13:15:39 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49358BED.3030903@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org>
Message-ID: <200812021559.05492.jhb@freebsd.org>

On Tuesday 02 December 2008 02:26:37 pm Alexander Motin wrote:
> Nate Lawson wrote:
> >> The only strange effect I have noticed was incorrect CPU time some
> >> processes got:
> >> %ps ax
> >>   PID  TT  STAT      TIME COMMAND
> >>    12  ??  WL   280503:38,05 [intr]
> >>  1430  ??  Ss   280503:38,34 icewm
> >>
> >> But I think it is more timer driver related then resume itself.
> > 
> > If you are using the LAPIC timer (default), it won't be running properly
> > during resume.  However, this wide discrepancy seems to indicate that
> > the timer state is not being resumed properly.  What if you use the ACPI
> > timer (hw.timecounter.* I think are the sysctls)?
> 
> As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast 
> as time source and TSC as kernel DELAY() source.
> 
> %sysctl -a | grep timecounter
> kern.timecounter.tick: 1
> kern.timecounter.choice: TSC(-100) ACPI-fast(1000) HPET(900) i8254(0) 
> dummy(-1000000)
> kern.timecounter.hardware: ACPI-fast
> kern.timecounter.nsetclock: 3
> kern.timecounter.ngetmicrotime: 353840
> kern.timecounter.ngetnanotime: 481
> kern.timecounter.ngetbintime: 0
> kern.timecounter.ngetmicrouptime: 2014472
> kern.timecounter.ngetnanouptime: 8950060
> kern.timecounter.ngetbinuptime: 419099
> kern.timecounter.nmicrotime: 1460084
> kern.timecounter.nnanotime: 40830
> kern.timecounter.nbintime: 1500942
> kern.timecounter.nmicrouptime: 2210
> kern.timecounter.nnanouptime: 21
> kern.timecounter.nbinuptime: 1988392
> kern.timecounter.stepwarnings: 0
> kern.timecounter.tc.i8254.mask: 65535
> kern.timecounter.tc.i8254.counter: 46767
> kern.timecounter.tc.i8254.frequency: 1193182
> kern.timecounter.tc.i8254.quality: 0
> kern.timecounter.tc.HPET.mask: 4294967295
> kern.timecounter.tc.HPET.counter: 3274417396
> kern.timecounter.tc.HPET.frequency: 14318180
> kern.timecounter.tc.HPET.quality: 900
> kern.timecounter.tc.ACPI-fast.mask: 16777215
> kern.timecounter.tc.ACPI-fast.counter: 14616414
> kern.timecounter.tc.ACPI-fast.frequency: 3579545
> kern.timecounter.tc.ACPI-fast.quality: 1000
> kern.timecounter.tc.TSC.mask: 4294967295
> kern.timecounter.tc.TSC.counter: 3757339660
> kern.timecounter.tc.TSC.frequency: 2394021468
> kern.timecounter.tc.TSC.quality: -100
> kern.timecounter.smp_tsc: 0
> kern.timecounter.invariant_tsc: 1
> 
> There is sure some problem with LAPIC:
> %vmstat -i
> interrupt                          total       rate
> .....
> irq257: bge0                       70774         29
> cpu1: timer                        17600          7
> cpu1: timer                        27617         11
> cpu1: timer                        15849          6
> cpu1: timer                        15413          6
> cpu1: timer                       877180        367
> Total                            2284801        957

Oh, it's getting a new counter on each resume.  That is a bug.  Ah, I think 
the AP's are using lapic_setup(1) when they should be using lapic_setup(0) 
during a resume.

-- 
John Baldwin
From mav at FreeBSD.org  Tue Dec  2 13:37:29 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Tue Dec  2 13:37:41 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <200812021559.05492.jhb@freebsd.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org>
	<200812021559.05492.jhb@freebsd.org>
Message-ID: <4935AA86.7090405@FreeBSD.org>

John Baldwin wrote:
> Oh, it's getting a new counter on each resume.  That is a bug.  Ah, I think 
> the AP's are using lapic_setup(1) when they should be using lapic_setup(0) 
> during a resume.

Thanks. With this LAPIC works better:
--- mp_machdep.c.prev2  2008-12-02 23:33:10.000000000 +0200
+++ mp_machdep.c        2008-12-02 23:26:23.000000000 +0200
@@ -1127,7 +1127,7 @@ cpususpend_handler(void)
                 atomic_set_int(&stopped_cpus, cpumask);
         } else {
                 /* Set up local APIC again. */
-               lapic_setup(1);
+               lapic_setup(0);
         }

         while (!(started_cpus & cpumask))

But statistic problem is still here:
# ps ax
   PID  TT  STAT      TIME COMMAND
  1429  ??  Ss   282031:03,98 icewm

-- 
Alexander Motin
From brde at optusnet.com.au  Wed Dec  3 10:33:34 2008
From: brde at optusnet.com.au (Bruce Evans)
Date: Wed Dec  3 10:33:46 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49358BED.3030903@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org>
	<49358BED.3030903@FreeBSD.org>
Message-ID: <20081203210228.R1989@delplex.bde.org>

On Tue, 2 Dec 2008, Alexander Motin wrote:

> Nate Lawson wrote:
>>> The only strange effect I have noticed was incorrect CPU time some
>>> processes got:
>>> %ps ax
>>>   PID  TT  STAT      TIME COMMAND
>>>    12  ??  WL   280503:38,05 [intr]
>>>  1430  ??  Ss   280503:38,34 icewm
>>> 
>>> But I think it is more timer driver related then resume itself.
>> 
>> If you are using the LAPIC timer (default), it won't be running properly
>> during resume.  However, this wide discrepancy seems to indicate that
>> the timer state is not being resumed properly.  What if you use the ACPI
>> timer (hw.timecounter.* I think are the sysctls)?
>
> As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast as 
> time source and TSC as kernel DELAY() source.

CPU times use mainly the cpu_ticker (TSC on i386), and the cpu_ticker code
has always been broken if the frequency changes a lot.  The main bugs that
I know about are:
(1) the cpu time is (total cpu_ticks) / cputick_frequency(now) but should be
     the integral over previous thread history of
 		    (delta cpu_ticks) / cputick_frequency(t) dt.
     The former gives a wrong value if cputick_frequency(t) is not
     constant over previous thread history, and the wrongness is very
     obvious for long-running threads like intr and idle ones if the
     TSC frequency changes significantly (e.g., by cpufreq).  cpufreq
     has a callback to reinitialize the frequency calibration, but this
     doesn't help much.  I can't find any resume method for the TSC.

(2) frequency _re_calibration is broken.  It never decreases the frequency.
     Thus if the frequency is transiently high, the transiently high
     calibration persists until the next reinitialization of the frequency
     calibration (or until a tranisiently higher frequency is seen).
     Small variations due to temperature changes thus make the frequency
     persistently slightly higher that it should be, and large variations
     due to stopping a timer or stopping or throttling the TSC can make
     the freqency persistently very wrong.  This wrongness is very
     obvious using ddb.  While in ddb, interrupt timers are stopped but
     the TSC advances.  Recalibration then gives an enormously high
     frequency (nearly 1/0 = infinity) that is sticky due to the bug.
     Dividing by this then gives all cpu times of nearly 0, modulo
     monotonicity enforcement by calcru() (which helps here -- old
     nonzero times for intr and idle remain nonzero).  The sanity checking
     in the recalibration detects remarkably few cases of insanity for
     some reason, perhaps because the timers are too in sync.

You seem to have the opposite problem, that times are enormously high.
This would be caused by the frequency being calibrated as nearly 0,
but I can't see how this could happen -- the TSC is presumably stopped
while the system is suspended, so the recalibration code would tend
to give a frequency far too low if the resume method is indeed missing,
but bug (2) prevents this low value being used; OTOH, the resume method
should recalibrate only after restarting all clocks, so it shouldn't
suffer from bug (2).  There are possible races getting the calibration
done by the resume method before the main timer interrupt handler does
it based on bogus data, but the latter doesn't happen on every timer
interrupt so you would be unlucky to lose these races.

If the frequency is transiently miscalibrated as nearly 0 and you look
at the cpu time using calcru() during this time, then bug (1) gives
enormously high times like the above (nearly 1/0) for long running
processes; then calcru()'s monotonicity enforcement preserves the
enormously high times almost forever (recalibration should eventually
fix the frequency, so bug (1) would give normal times again since
nothing much has happened to the tick counts; however monotonicity
enforcement results in the transiently high times being returned almost
forever -- the returned times won't even increase until the normal
times reach the enormous value or another transient miscalibration
messes up the calculation of the raw times again).

Bruce
From franks at rudbek.com  Wed Dec  3 13:59:26 2008
From: franks at rudbek.com (Steve Franks)
Date: Wed Dec  3 14:15:56 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <200812021243.08513.jkim@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org>
Message-ID: <539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com>

On Tue, Dec 2, 2008 at 10:43 AM, Jung-uk Kim <jkim@freebsd.org> wrote:
> On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote:
>> Hi.
>>
>> Alexander Motin wrote:
>> > Jung-uk Kim wrote:
>> >> I was working on suspend/resume support for amd64 and this is
>> >> the result.  It works with a modified QEMU (QEMU does not
>> >> support S3) but real boxes that I have don't seem to like it
>> >> (e.g., broken BIOSes). If there is someone interested in
>> >> finishing it off or giving it a try, the patch is here:
>> >>
>> >> http://people.freebsd.org/~jkim/amd64_suspend.diff
>> >
>> > I have tried it on my Acer TM6292. S1/S2 are unsupported. On S3
>> > system successfully got down, but on wakeup button, two seconds
>> > after power up, even without video initialization, it shut down,
>> > reset and then started usual boot. I have tried both original and
>> > updated BIOS, without any difference.
>> >
>> > Can I give you any other help?
>>
>> I have spent a day investigating the problem. I was inserting empty
>> infinite loop into the different points of wakeup process trying to
>> find the place where system reboots. I just haven't found any other
>> feedback channel as video is not initialized and beeper is not
>> working for some reason.
>>
>> As result, I have found, that if I am inserting:
>> qqq:
>>
>>          jmp     qqq
>> lines before line 98 of acpi_switch.S:
>>       movl    $MSR_MTRRdefType, %ecx
>>
>>          movl    WAKEUP_CTX(mtrr), %eax
>>
>>          wrmsr
>> system hangs, but if I insert it just after them - system reboots.
>>
>> With just commenting this three lines I was able to get successful
>> suspend/resume with UP amd64 kernel!!!
>
> Good catch!  I can confirm this is a correct bandaid.  We cannot
> restore this MSR without restoring entire MTRR map.  Actually, I
> should have written separate functions to save/restore all global
> MSRs.  Only per-CPU MSRs should be embedded like that.
>
>> Here is problems I still have now:
>>   - SMP kernel resume is not working, system reboots while doing
>> acpi_wakeup_cpus();
>
> My dual-core CPU seems to resume okay but quite unstable.  Can you try
> something like the following in amd64/mp_machdep.c and tell me if it
> helps?
>
> ------------
> @@ -57,6 +57,7 @@
>  #include <vm/vm_extern.h>
>
>  #include <machine/apicreg.h>
> +#include <machine/cpufunc.h>
>  #include <machine/md_var.h>
>  #include <machine/mp_watchdog.h>
>  #include <machine/pcb.h>
> @@ -1121,6 +1121,8 @@
>        int cpumask = PCPU_GET(cpumask);
>
>        if (savectx2(&stopxpcbs[cpu])) {
> +               /* Flush CPU cache. */
> +               wbinvd();
>                /* Indicate that we are suspended. */
>                atomic_set_int(&stopped_cpus, cpumask);
>        } else {
> ------------
>
>>   - text mode video does not restores on resume, while Xorg graphic
>> one does. hw.acpi.reset_video=1 does not help, it just hanging
>> resume process.
>
> It is very common problem for modern video cards.  We cannot do much
> here without help of GPU-specific routines (e.g., ATI ATOM BIOS
> parser for RadeonHD) or in-kernel realmode emulation[1] (e.g.,
> NetBSD).
>
> Thanks for the feedback!
>
> Jung-uk Kim
>
> [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/
> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c
> _______________________________________________
> freebsd-acpi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"
>

Do you believe these patches should work against 6.4?  I should like
to try it out on my trusty 'ol desktop.

Best,
Steve
From franks at rudbek.com  Wed Dec  3 15:14:41 2008
From: franks at rudbek.com (Steve Franks)
Date: Wed Dec  3 15:15:55 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org>
	<539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com>
Message-ID: <539c60b90812031514x3246ca09ua2febc879f8a7fcf@mail.gmail.com>

> On Tue, Dec 2, 2008 at 10:43 AM, Jung-uk Kim <jkim@freebsd.org> wrote:
>> On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote:
>>> Hi.
>>>
>>> Alexander Motin wrote:
>>> > Jung-uk Kim wrote:
>>> >> I was working on suspend/resume support for amd64 and this is
>>> >> the result.  It works with a modified QEMU (QEMU does not
>>> >> support S3) but real boxes that I have don't seem to like it
>>> >> (e.g., broken BIOSes). If there is someone interested in
>>> >> finishing it off or giving it a try, the patch is here:
>>> >>
>>> >> http://people.freebsd.org/~jkim/amd64_suspend.diff
>>> >
>>> > I have tried it on my Acer TM6292. S1/S2 are unsupported. On S3
>>> > system successfully got down, but on wakeup button, two seconds
>>> > after power up, even without video initialization, it shut down,
>>> > reset and then started usual boot. I have tried both original and
>>> > updated BIOS, without any difference.
>>> >
>>> > Can I give you any other help?
>>>
>>> I have spent a day investigating the problem. I was inserting empty
>>> infinite loop into the different points of wakeup process trying to
>>> find the place where system reboots. I just haven't found any other
>>> feedback channel as video is not initialized and beeper is not
>>> working for some reason.
>>>
>>> As result, I have found, that if I am inserting:
>>> qqq:
>>>
>>>          jmp     qqq
>>> lines before line 98 of acpi_switch.S:
>>>       movl    $MSR_MTRRdefType, %ecx
>>>
>>>          movl    WAKEUP_CTX(mtrr), %eax
>>>
>>>          wrmsr
>>> system hangs, but if I insert it just after them - system reboots.
>>>
>>> With just commenting this three lines I was able to get successful
>>> suspend/resume with UP amd64 kernel!!!
>>
>> Good catch!  I can confirm this is a correct bandaid.  We cannot
>> restore this MSR without restoring entire MTRR map.  Actually, I
>> should have written separate functions to save/restore all global
>> MSRs.  Only per-CPU MSRs should be embedded like that.
>>
>>> Here is problems I still have now:
>>>   - SMP kernel resume is not working, system reboots while doing
>>> acpi_wakeup_cpus();
>>
>> My dual-core CPU seems to resume okay but quite unstable.  Can you try
>> something like the following in amd64/mp_machdep.c and tell me if it
>> helps?
>>
>> ------------
>> @@ -57,6 +57,7 @@
>>  #include <vm/vm_extern.h>
>>
>>  #include <machine/apicreg.h>
>> +#include <machine/cpufunc.h>
>>  #include <machine/md_var.h>
>>  #include <machine/mp_watchdog.h>
>>  #include <machine/pcb.h>
>> @@ -1121,6 +1121,8 @@
>>        int cpumask = PCPU_GET(cpumask);
>>
>>        if (savectx2(&stopxpcbs[cpu])) {
>> +               /* Flush CPU cache. */
>> +               wbinvd();
>>                /* Indicate that we are suspended. */
>>                atomic_set_int(&stopped_cpus, cpumask);
>>        } else {
>> ------------
>>
>>>   - text mode video does not restores on resume, while Xorg graphic
>>> one does. hw.acpi.reset_video=1 does not help, it just hanging
>>> resume process.
>>
>> It is very common problem for modern video cards.  We cannot do much
>> here without help of GPU-specific routines (e.g., ATI ATOM BIOS
>> parser for RadeonHD) or in-kernel realmode emulation[1] (e.g.,
>> NetBSD).
>>
>> Thanks for the feedback!
>>
>> Jung-uk Kim
>>
>> [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/
>> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c
>> _______________________________________________
>> freebsd-acpi@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
>> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"
>>
>

Do you believe these patches should work against 6.4?  I should like
to try it out on my trusty 'ol desktop.

Best,
Steve
From mav at FreeBSD.org  Wed Dec  3 16:07:17 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Wed Dec  3 16:07:30 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <20081203210228.R1989@delplex.bde.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org>
	<200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org>
	<49358BED.3030903@FreeBSD.org>
	<20081203210228.R1989@delplex.bde.org>
Message-ID: <4937181F.5000009@FreeBSD.org>

Bruce Evans wrote:
> On Tue, 2 Dec 2008, Alexander Motin wrote:
>> Nate Lawson wrote:
>>>> The only strange effect I have noticed was incorrect CPU time some
>>>> processes got:
>>>> %ps ax
>>>>   PID  TT  STAT      TIME COMMAND
>>>>    12  ??  WL   280503:38,05 [intr]
>>>>  1430  ??  Ss   280503:38,34 icewm
>>>>
>>>> But I think it is more timer driver related then resume itself.
>>>
>>> If you are using the LAPIC timer (default), it won't be running properly
>>> during resume.  However, this wide discrepancy seems to indicate that
>>> the timer state is not being resumed properly.  What if you use the ACPI
>>> timer (hw.timecounter.* I think are the sysctls)?
>>
>> As I understand, I am now using LAPIC timer for HZ generation, 
>> ACPI-fast as time source and TSC as kernel DELAY() source.
> 
> CPU times use mainly the cpu_ticker (TSC on i386), and the cpu_ticker code
> has always been broken if the frequency changes a lot.  The main bugs that
> I know about are:

Latest CPUs, including mine, does not change TSC frequency with EST and 
Cx states. So I think it is not frequency problem.

I haven't checked if it specially handled, but I think, that when system 
suspended, timers may not be just stopped, but could also be reseted. If 
CPU looses all it's context, why should it keep some timer state? If 
timer reseted - it's value probably will go back, that may be seen as 
negative overflow.

Here is some more related error messages I have found on resume:

kernel: calcru: runtime went backwards from 5095 usec to 12 usec for pid 
1544 (sh)
kernel: calcru: runtime went backwards from 4704 usec to 12 usec for pid 
1544 (sh)
kernel: calcru: runtime went backwards from 1279 usec to 2 usec for pid 
1543 (sh)
kernel: calcru: runtime went backwards from 4180 usec to 9 usec for pid 
1511 (moused)
kernel: calcru: runtime went backwards from 11869 usec to 26 usec for 
pid 1435 (csh)
kernel: calcru: runtime went backwards from 46399 usec to 102 usec for 
pid 1435 (csh)
kernel: calcru: runtime went backwards from 4377 usec to 9 usec for pid 
1434 (su)
kernel: calcru: runtime went backwards from 10097 usec to 22 usec for 
pid 1432 (csh)

-- 
Alexander Motin
From neldredge at math.ucsd.edu  Wed Dec  3 16:50:05 2008
From: neldredge at math.ucsd.edu (Nate Eldredge)
Date: Wed Dec  3 16:50:14 2008
Subject: amd64/128259: csh(1): "`" crashes csh
Message-ID: <200812040050.mB40o5Fc014825@freefall.freebsd.org>

The following reply was made to PR amd64/128259; it has been noted by GNATS.

From: Nate Eldredge <neldredge@math.ucsd.edu>
To: bug-followup@FreeBSD.org, xxjack12xx@gmail.com
Cc:  
Subject: Re: amd64/128259: csh(1): "`" crashes csh
Date: Wed, 3 Dec 2008 16:42:09 -0800 (PST)

 This is incorporated into bin/129405.
 
 -- 
 
 Nate Eldredge
 neldredge@math.ucsd.edu
From prox at prolixium.com  Thu Dec  4 15:20:02 2008
From: prox at prolixium.com (Mark Kamichoff)
Date: Thu Dec  4 16:11:58 2008
Subject: amd64/129426: FreeBSD 7.0 crash after subdiskXX: detached
Message-ID: <200812042315.mB4NFsbV026394@www.freebsd.org>


>Number:         129426
>Category:       amd64
>Synopsis:       FreeBSD 7.0 crash after subdiskXX: detached
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 04 23:20:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mark Kamichoff
>Release:        FreeBSD 7.0-RELEASE-p1
>Organization:
>Environment:
FreeBSD dax.prolixium.com 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #0: Thu May 22 22:20:18 EDT 2008     prox@dax1.prolixium.com:/usr/obj/usr/src/sys/DAX  amd64
>Description:
Hi - 

Every 30-60 days my FreeBSD-7 server will crash with the following output:

subdisk12: detached
ad12: detached
g_vfs_done():ad12s1d[WRITE(offset=160650805248, length=16384)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=67040542720, length=16384)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=80158326784, length=16384)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=160691107840, length=2048)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=155648786432, length=2048)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=6144000, length=16384)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=6160384, length=6144)]error = 6
g_vfs_done():ad12s1d[WRITE(offset=65536, length=2048)]error = 6
g_vfs_done():ad12s1d[READ(offset=160702988288, length=16384)]error = 6
g_vfs_done():ad12s1d[READ(offset=160710213632, length=16384)]error = 6
panic: vinvalbuf: dirty bufs
cpuid = 0
Uptime: 30d8h8m29s
Physical memory: 998 MB
Dumping 316 MB: 301 285 269 253 237 221 205 ... <serial console output hangs>

This has been happening since the box was built about two years ago, initially running FreeBSD 6.1.  I've replaced all the hardware in this box recently (including the chassis) and upgraded to FreeBSD 7.0.  The crashes are all the same, varying only in the disk that becomes detached (subdisk12 or subdisk8 - either 250GB SATA disk).

I haven't been able to obtain a dump of physical memory, since the machine always hard locks halfway through the dump operation.  Since this is a dedicated server at a colocation facility, I don't have physical access to the server - only serial console.

Please let me know what information to provide.  Since I have replaced all the hardware in the machine at this point, I believe this can be eliminated as a possible culprit.

Thanks!

- Mark
>How-To-Repeat:
Unknown.  Box has never attained uptime for more than 100-120 days, though.
>Fix:
Unknown.

>Release-Note:
>Audit-Trail:
>Unformatted:
From kumark at vmware.com  Sun Dec  7 01:00:05 2008
From: kumark at vmware.com (Kumar Krishnamoorthy)
Date: Sun Dec  7 04:38:04 2008
Subject: amd64/128978: [install] FreeBSD 6.3 64-bit panics at boot time
 during installation on HP DL580 G5 with 128GB physical memory
Message-ID: <200812070900.mB7905Ia071906@freefall.freebsd.org>

The following reply was made to PR amd64/128978; it has been noted by GNATS.

From: Kumar Krishnamoorthy <kumark@vmware.com>
To: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org>, Kumar
 Krishnamoorthy <kumark@vmware.com>
Cc:  
Subject: Re: amd64/128978: [install] FreeBSD 6.3 64-bit  panics at boot time
 during installation on HP DL580 G5 with 128GB physical memory
Date: Sun, 7 Dec 2008 00:50:55 -0800

 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D65PAEXMBX04vmwa_
 Content-Type: text/plain; charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 This is from freeBSD6.4 64 GA
 SMAP type=3D01 base=3D0000000000000000   len 000000000009f800
 SMAP type=3D02 base=3D000000000009f800    len 0000000000000800
 SMAP type=3D02 base=3D00000000000ca000   len 0000000000002000
 SMAP type=3D02 base=3D00000000000dc000   len 0000000000004000
 SMAP type=3D02 base=3D00000000000e4000   len 000000000001c000
 SMAP type=3D01 base=3D0000000000100000   len 00000000bfdf0000
 SMAP type=3D03 base=3D00000000bfef0000     len 000000000000f000
 SMAP type=3D04 base=3D00000000bfeff000      len 0000000000001000
 SMAP type=3D01 base=3D00000000bff00000     len 0000000000100000
 SMAP type=3D02 base=3D00000000e0000000   len 0000000010000000
 SMAP type=3D02 base=3D00000000fec00000    len 0000000000010000
 SMAP type=3D02 base=3D00000000fee00000    len 0000000000001000
 SMAP type=3D02 base=3D00000000fffe0000      len 0000000000020000
 SMAP type=3D01 base=3D0000000100000000   len 0000001f40000000
 
 I could not reproduce this on freeBSD7.0 GA. It boots well without any issu=
 es.
 
 -Kumar
 
 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D65PAEXMBX04vmwa_
 Content-Type: text/html; charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
 <META content=3D"MSHTML 6.00.3790.4357" name=3DGENERATOR></HEAD>
 <BODY>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2>This is f=
 rom=20
 freeBSD6.4 64 GA</FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=
 =3D01=20
 base=3D0000000000000000&nbsp; &nbsp;len 000000000009f800</FONT></SPAN></DIV=
 >
 <DIV><SPAN class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=
 =3D02=20
 base=3D000000000009f800&nbsp;&nbsp;&nbsp; len 0000000000000800</FONT></SPAN=
 ></DIV>
 <DIV><SPAN class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=
 =3D02=20
 base=3D00000000000ca000&nbsp;&nbsp; len 0000000000002000</FONT></SPAN></DIV=
 >
 <DIV><SPAN class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000000dc000&nbsp;&nbsp; len=20
 0000000000004000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000000e4000&nbsp;&nbsp; len=20
 000000000001c000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D01=20
 base=3D0000000000100000&nbsp;&nbsp; len=20
 00000000bfdf0000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D03=20
 base=3D00000000bfef0000&nbsp;&nbsp;&nbsp;&nbsp; len=20
 000000000000f000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D04=20
 base=3D00000000bfeff000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;len=20
 0000000000001000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D01=20
 base=3D00000000bff00000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;len=20
 0000000000100000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000e0000000&nbsp;&nbsp;&nbsp;len=20
 0000000010000000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000fec00000&nbsp;&nbsp;&nbsp; len=20
 0000000000010000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000fee00000&nbsp;&nbsp;&nbsp;&nbsp;len=20
 0000000000001000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D02=20
 base=3D00000000fffe0000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; len=20
 0000000000020000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008><FONT face=3DArial size=3D2>SMAP type=3D01=20
 base=3D0000000100000000&nbsp;&nbsp; len=20
 0000001f40000000</FONT></SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008></SPAN></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>I could not reproduce this on freeBSD7.0 GA. It =
 boots=20
 well without any issues.</SPAN></FONT></SPAN></DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008></SPAN></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=3D388412308-07122008><FONT face=3DArial size=3D2><SPAN=20
 class=3D388412308-07122008>-Kumar</SPAN></FONT></SPAN></DIV></SPAN></FONT><=
 /SPAN></DIV></SPAN></FONT></SPAN></DIV></SPAN></FONT></SPAN></DIV></SPAN></=
 FONT></SPAN></DIV></SPAN></FONT></SPAN></DIV></SPAN></FONT></SPAN></DIV></S=
 PAN></FONT></SPAN></DIV></SPAN></FONT></SPAN></DIV></SPAN></FONT></SPAN></D=
 IV></SPAN></FONT></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></DIV></BODY=
 ></HTML>
 
 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D65PAEXMBX04vmwa_--
From eric+freebsd.org at lame.net  Sun Dec  7 14:30:01 2008
From: eric+freebsd.org at lame.net (Eric Sabban)
Date: Sun Dec  7 14:57:52 2008
Subject: amd64/129488: Kernel "bug" when using smbfs in smbfs_smb.c: kernel:
	bug: ecnt = 1, but m_len = 0 and m_next = 0
Message-ID: <200812072221.mB7ML7Br016042@www.freebsd.org>


>Number:         129488
>Category:       amd64
>Synopsis:       Kernel "bug" when using smbfs in smbfs_smb.c: kernel: bug: ecnt = 1, but m_len = 0 and m_next = 0
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec 07 22:30:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Eric Sabban
>Release:        7.0-RELEASE-p7
>Organization:
none
>Environment:
FreeBSD sekret.lame.net 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #3: Thu Dec  4 21:48:54 PST 2008     root@sekret.lame.net:/usr/obj/usr/src/sys/SEKRET  amd64

>Description:
Shortly after booting the fileserver (leopard g5) and the smb client (freebsd 7.0p6) I mounted two disks over smb (mount //eric@g5/blah)  from the server. I did an awful thing, just for the sake of it:

for i in *.avi; do file=`echo ${i} | sed -e 's/.avi$//'`; ffmpeg -i "${file}.avi" "/usr/tmp/${file}.mp4" > /tmp/ffmpeg.$$ 2>&1 & done

Ugly as that may have been, the kernel then spit out:

smb_iod_recvall: drop resp with mid 4526
smb_iod_recvall: drop resp with mid 4527
smb_iod_recvall: drop resp with mid 4528
smb_iod_recvall: drop resp with mid 4530
smb_iod_recvall: drop resp with mid 4531
bug: ecnt = 1, but m_len = 0 and m_next = 0 (please report)

Nothing really HAPPENED, but you asked me to report, so here I am.

>How-To-Repeat:
Start out a bunch of concurrent I/O from a fileserver that likely cannot handle it, I did it shortly after booting both the fileserver and the client.
>Fix:
If only I knew.


>Release-Note:
>Audit-Trail:
>Unformatted:
From kumark at vmware.com  Mon Dec  8 00:00:11 2008
From: kumark at vmware.com (Kumar Krishnamoorthy)
Date: Mon Dec  8 04:25:03 2008
Subject: amd64/128978: [install] FreeBSD 6.3 64-bit panics at boot time
 during installation on HP DL580 G5 with 128GB physical memory
Message-ID: <200812080800.mB880BY1067740@freefall.freebsd.org>

The following reply was made to PR amd64/128978; it has been noted by GNATS.

From: Kumar Krishnamoorthy <kumark@vmware.com>
To: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org>, Kumar
 Krishnamoorthy <kumark@vmware.com>
Cc:  
Subject: Re: amd64/128978: [install] FreeBSD 6.3 64-bit  panics at boot time
 during installation on HP DL580 G5 with 128GB physical memory
Date: Sun, 7 Dec 2008 23:50:40 -0800

 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D98PAEXMBX04vmwa_
 Content-Type: text/plain; charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 I could see the failure on all freebsd6.x-64 with more than 64GB of memory.=
   I ran this test on virtual machine that was created on the same HP DL580 =
 G5 server with 128GB server.
 Failures
   7 FAIL Duration=3D15m29s guestOS=3Dfreebsd6.2-64           memSize=3D1310=
 72
   8 FAIL Duration=3D15m35s guestOS=3Dfreebsd6.3-64           memSize=3D1310=
 72
   9 FAIL Duration=3D15m33s guestOS=3Dfreebsd6.4-beta1-64 memSize=3D131072
  10 FAIL Duration=3D15m32s guestOS=3Dfreebsd6.4-rc1-64    memSize=3D131072
  11 FAIL Duration=3D15m32s guestOS=3Dfreebsd6.4-rc2-64    memSize=3D131072
 Passed
   0 PASS Duration=3D46m53s guestOS=3Dfreebsd6.2-64          memSize=3D65536
   1 PASS Duration=3D52m48s guestOS=3Dfreebsd6.3-64          memSize=3D65536
   3 PASS Duration=3D23m14s guestOS=3Dfreebsd6.4-rc1-64    memSize=3D65536
   4 PASS Duration=3D23m20s guestOS=3Dfreebsd6.4-rc2-64    memSize=3D65536 .=
 .
 memSize - Guest memory that was used for the test in MB.
 Duration  -  Time it tool to install the guestOS.
 
 
 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D98PAEXMBX04vmwa_
 Content-Type: text/html; charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
 <META content=3D"MSHTML 6.00.3790.4357" name=3DGENERATOR></HEAD>
 <BODY>
 <DIV class=3Dnorm><SPAN class=3D890154207-08122008></SPAN><FONT face=3DAria=
 l>I<SPAN=20
 class=3D890154207-08122008> could see the&nbsp;failure on all freebsd6.x-64=
  with=20
 more than 64GB of memory.&nbsp;&nbsp;I ran this test on&nbsp;virtual machin=
 e=20
 that was created on the same HP DL580 G5 server with=20
 128GB&nbsp;server.</SPAN></FONT><BR><SPAN class=3D890154207-08122008><FONT=
 =20
 face=3DArial size=3D2>Failures</FONT></SPAN></DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;7 FAIL Duration=3D15m29s=20
 guestOS=3Dfreebsd6.2-64&nbsp;<SPAN=20
 class=3D890154207-08122008>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 &nbsp;=20
 </SPAN>memSize=3D131072&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;8 FAIL Duration=3D15m35s=20
 guestOS=3Dfreebsd6.3-64&nbsp;<SPAN=20
 class=3D890154207-08122008>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 &nbsp;=20
 </SPAN>memSize=3D131072&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;9 FAIL Duration=3D15m33s guestOS=3Dfreebsd6.4=
 -beta1-64=20
 memSize=3D131072</DIV>
 <DIV class=3Dnorm>&nbsp;10 FAIL Duration=3D15m32s=20
 guestOS=3Dfreebsd6.4-rc1-64&nbsp;<SPAN class=3D890154207-08122008>&nbsp;&nb=
 sp;=20
 </SPAN>memSize=3D131072&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;11 FAIL Duration=3D15m32s=20
 guestOS=3Dfreebsd6.4-rc2-64&nbsp;<SPAN class=3D890154207-08122008>&nbsp;=20
 &nbsp;</SPAN>memSize=3D131072&nbsp;</DIV>
 <DIV class=3Dnorm><SPAN class=3D890154207-08122008>Passed</SPAN></DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;0 PASS Duration=3D46m53s=20
 guestOS=3Dfreebsd6.2-64&nbsp;<SPAN=20
 class=3D890154207-08122008>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =20
 </SPAN>memSize=3D65536&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;1 PASS Duration=3D52m48s=20
 guestOS=3Dfreebsd6.3-64&nbsp;<SPAN=20
 class=3D890154207-08122008>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =20
 </SPAN>memSize=3D65536&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;3 PASS Duration=3D23m14s=20
 guestOS=3Dfreebsd6.4-rc1-64&nbsp;<SPAN class=3D890154207-08122008>&nbsp;&nb=
 sp;=20
 </SPAN>memSize=3D65536&nbsp;</DIV>
 <DIV class=3Dnorm>&nbsp;&nbsp;4 PASS Duration=3D23m20s=20
 guestOS=3Dfreebsd6.4-rc2-64&nbsp;<SPAN class=3D890154207-08122008>&nbsp;&nb=
 sp;=20
 </SPAN>memSize=3D65536 ..<BR></DIV>
 <DIV><FONT face=3DArial size=3D2><SPAN class=3D890154207-08122008>memSize -=
 &nbsp;Guest=20
 memory that was used for the test in MB.</SPAN></FONT></DIV>
 <DIV><FONT face=3DArial size=3D2><SPAN=20
 class=3D890154207-08122008>Duration&nbsp;&nbsp;-&nbsp;&nbsp;Time it tool to=
 =20
 install the guestOS.</SPAN></FONT></DIV>
 <DIV><FONT face=3DArial size=3D2><SPAN=20
 class=3D890154207-08122008></SPAN></FONT>&nbsp;</DIV></BODY></HTML>
 
 --_000_7A7D327E99D30143AC98BDABFCABFF012271549D98PAEXMBX04vmwa_--
From bugmaster at FreeBSD.org  Mon Dec  8 03:06:52 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Dec  8 04:25:44 2008
Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org
Message-ID: <200812081106.mB8B6p6I014181@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/129488 amd64      [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: 
o amd64/129426 amd64      [panic] FreeBSD 7.0 crash after subdiskXX: detached
o amd64/129315 amd64      [boot] amd64 motherboard: Intel DG965WH motherboard co
o amd64/129238 amd64      [panic] System randomly panics
f amd64/128978 amd64      [install] FreeBSD 6.3 64-bit  panics at boot time duri
o amd64/128810 amd64      AMD 64 port installation
o amd64/128765 amd64      [install] Install CD loads to Install choices but stop
o amd64/128686 amd64      [ata] can't detect SATA Disk on 8.0-Current with NF550
o amd64/128524 amd64      No geom documentation for loading gjournal
o amd64/128263 amd64      [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a
o amd64/128259 amd64      csh(1): "`" crashes csh
o amd64/128236 amd64      portsdb -Uu Indexing error
f kern/128102  amd64      AsusRock 939N68PV-GLAN not recognized
o amd64/127787 amd64      [lor] 3 lock LOR in recent CURRENT
o amd64/127640 amd64      GCC will not build shared libraries with -fprofile-gen
o amd64/127492 amd64      [zfs] System hang on ZFS input-output
o amd64/127484 amd64      [timecounters] Drift problem with FreeBSD 7.0 and 7.1 
o amd64/127451 amd64      [scheduler] incorrect load on quad core
o amd64/127397 amd64      [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI
s amd64/127276 amd64      ldd(1) invokes linux yes
o amd64/127129 amd64      mdconfig(8) is core dumping with Segmentation Fault 11
f amd64/125943 amd64      Serial Consoles do not work on amd64 freebsd
o amd64/125873 amd64      [smbd] [panic] Repeated kernel panics, trap 12 page fa
o amd64/125002 amd64      [install] amd64, SATA hard disks not detected
o amd64/124432 amd64      [panic] 7.0-STABLE panic: invalbuf: dirty bufs
o amd64/124134 amd64      [kernel] The kernel doesn't follow the calling convent
o amd64/123562 amd64      [install] FreeBSD amd64 not installs
o amd64/123520 amd64      [ahd] unable to boot from net while using ahd
o amd64/123456 amd64      fstat(1): /usr/bin/fstat shows error messages and hang
f amd64/123275 amd64      [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re
o kern/122782  amd64      [modules] accf_http.ko kernel module is not loadable
o amd64/122695 amd64      [cpufreq] Lack of cpufreq control using amd64 eith cor
o amd64/122624 amd64      unusable minimal installation of FreeBSD-7.0
o amd64/122549 amd64      7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial 
o amd64/122468 amd64      Compile problems after upgrading to 7.0
o amd64/122174 amd64      [panic] 7.0 no longer includes "device atpic" so fails
o amd64/121590 amd64      [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet
o amd64/121439 amd64      [boot] Installation of FreeBSD 7.0 fails: ACPI problem
o amd64/120202 amd64      [amd64] [patch] [panic] kernel panic at start_all_aps,
o amd64/119936 amd64      [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis
o amd64/119591 amd64      [amd64] [patch] time_t on 64-bit architecture
o amd64/117418 amd64      [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh
o amd64/117316 amd64      [acpi] ACPI lockups on SuperMicro motherboard
o amd64/117296 amd64      [ata] I don`t see second SATA IDE on VIA VT8237A
a amd64/117186 amd64      [modules] kldload Unsupported file type on STABLE amd6
s amd64/116689 amd64      [request] support for MSI K9MM-V
f amd64/116670 amd64      [ata] onboard SATA RAID1 controllers not supported for
o amd64/116620 amd64      [hang] ifconfig spins when creating carp(4) device on 
o amd64/116322 amd64      [panic] At start fsck on current, the system panics
o amd64/116159 amd64      [panic] Panic while debugging on CURRENT
s amd64/115815 amd64      [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp
o amd64/115581 amd64      [Makefile] [patch] -mfancy-math-387 has no effect
o amd64/115194 amd64      LCD screen remains blank after Dell XPS M1210 lid is c
o amd64/114270 amd64      [cpufreq] cpufreq doesnt work when compiled in to kern
o amd64/114111 amd64      [nfs] System crashes while writing on NFS-mounted shar
f amd64/113021 amd64      [re] ASUS M2A-VM onboard NIC does not work
o amd64/112222 amd64      [libc] 32-bit libc incorrectly converts some FP number
f amd64/111992 amd64      [boot] BTX failed - HP Laptop dv2315nr
o amd64/110655 amd64      [threads] 32 bit threaded applications crash on amd64 
o amd64/110599 amd64      [geli] geli attach to gmirror device hangs and cannot 
s amd64/108861 amd64      [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work
o amd64/106186 amd64      [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p
f amd64/105629 amd64      [re] TrendNet TEG-BUSR 10/100/1000 disables itself on 
f amd64/105531 amd64      [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does
f amd64/105514 amd64      [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv
o amd64/102716 amd64      ex with no argument in an xterm gets SIGSEGV
o amd64/97337  amd64      [dri] xorg reboots system if dri module is enabled
o amd64/95888  amd64      [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP 
f amd64/94989  amd64      [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64)
o amd64/94677  amd64      [panic] panic in amd64 install at non-root user creati
o amd64/93961  amd64      [busdma] Problem in bounce buffer handling in sys/amd6
o amd64/92337  amd64      [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff
f amd64/91492  amd64      [boot] BTX halted
o amd64/91405  amd64      [asr] [panic] Kernel panic caused by asr on 6.0-amd64 
o amd64/89501  amd64      [install] System crashes on install using ftp on local
o amd64/88790  amd64      [panic] kernel panic on first boot (after the FreeBSD 
o amd64/88568  amd64      [panic] 6.0-RELEASE install cd does not boot with usb 
o amd64/87689  amd64      [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE
o amd64/87316  amd64      [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6
o amd64/87305  amd64      [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in
f amd64/87258  amd64      [smp] [boot] cannot boot with SMP and Areca ARC-1160 r
f amd64/86080  amd64      [radeon] [hang] radeon DRI causes system hang on amd64
s amd64/85273  amd64      [install] FreeBSD (NetBSD or OpenBSD) not install on l
o amd64/78406  amd64      [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys
o amd64/76136  amd64      [hang] system halts before reboot
o amd64/74747  amd64      [panic] System panic on shutdown when process will not
o amd64/73322  amd64      [msdosfs] [hang] unarchiving /etc to msdosfs locks up 

87 problems total.

From bsditer at gmail.com  Mon Dec  8 20:30:02 2008
From: bsditer at gmail.com (Ven)
Date: Mon Dec  8 20:55:57 2008
Subject: amd64/129515: apache activemq always cause system reboot
Message-ID: <200812090422.mB94MvQb019126@www.freebsd.org>


>Number:         129515
>Category:       amd64
>Synopsis:       apache activemq always cause system reboot
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 09 04:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Ven
>Release:        6.3-RELEASE-amd64
>Organization:
Su2
>Environment:
FreeBSD aop.su-fun.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Aug 27 18:52:34 CST 2008     root@aop.su-fun.com:/usr/obj/usr/src/sys/aop  amd64

>Description:
system always reboot while quit apache activemq (http://activemq.apache.org/index.html)

same problem with diablo-jdk-freebsd6.amd64.1.5.0.07.01 and jdk 1.6.


>How-To-Repeat:
$ cd /usr/local/activemq/bin
$ ./activemq

<< press Ctrl+C to quit >>
.. then system reboot ...
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From neldredge at math.ucsd.edu  Mon Dec  8 21:33:49 2008
From: neldredge at math.ucsd.edu (Nate Eldredge)
Date: Mon Dec  8 21:33:55 2008
Subject: amd64/129515: apache activemq always cause system reboot
In-Reply-To: <200812090422.mB94MvQb019126@www.freebsd.org>
References: <200812090422.mB94MvQb019126@www.freebsd.org>
Message-ID: <Pine.GSO.4.64.0812082110070.22402@zeno.ucsd.edu>

On Tue, 9 Dec 2008, Ven wrote:

>
>> Number:         129515
>> Category:       amd64
>> Synopsis:       apache activemq always cause system reboot
>> Confidential:   no
>> Severity:       critical
>> Priority:       medium
>> Responsible:    freebsd-amd64
>> State:          open
>> Quarter:
>> Keywords:
>> Date-Required:
>> Class:          sw-bug
>> Submitter-Id:   current-users
>> Arrival-Date:   Tue Dec 09 04:30:01 UTC 2008
>> Closed-Date:
>> Last-Modified:
>> Originator:     Ven
>> Release:        6.3-RELEASE-amd64
>> Organization:
> Su2
>> Environment:
> FreeBSD aop.su-fun.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Aug 27 18:52:34 CST 2008     root@aop.su-fun.com:/usr/obj/usr/src/sys/aop  amd64
>
>> Description:
> system always reboot while quit apache activemq (http://activemq.apache.org/index.html)
>
> same problem with diablo-jdk-freebsd6.amd64.1.5.0.07.01 and jdk 1.6.
>
>
>> How-To-Repeat:
> $ cd /usr/local/activemq/bin
> $ ./activemq
>
> << press Ctrl+C to quit >>
> .. then system reboot ...
>> Fix:

Hi Ven,

This might be related to 
http://security.freebsd.org/advisories/FreeBSD-SA-08:07.amd64.asc .  I 
originally discovered the bug when running Java (a Linux binary in that 
case) caused the machine to reboot.  Could you please apply the patch 
http://security.FreeBSD.org/patches/SA-08:07/amd64.patch , or else upgrade 
to FreeBSD 6.3-RELEASE-p6 or 6.4-RELEASE, and see if the problem still 
appears?

-- 

Nate Eldredge
neldredge@math.ucsd.edu
From neldredge at math.ucsd.edu  Mon Dec  8 21:40:04 2008
From: neldredge at math.ucsd.edu (Nate Eldredge)
Date: Mon Dec  8 21:40:10 2008
Subject: amd64/129515: apache activemq always cause system reboot
Message-ID: <200812090540.mB95e3fV063680@freefall.freebsd.org>

The following reply was made to PR amd64/129515; it has been noted by GNATS.

From: Nate Eldredge <neldredge@math.ucsd.edu>
To: Ven <bsditer@gmail.com>
Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org
Subject: Re: amd64/129515: apache activemq always cause system reboot
Date: Mon, 8 Dec 2008 21:21:43 -0800 (PST)

 On Tue, 9 Dec 2008, Ven wrote:
 
 >
 >> Number:         129515
 >> Category:       amd64
 >> Synopsis:       apache activemq always cause system reboot
 >> Confidential:   no
 >> Severity:       critical
 >> Priority:       medium
 >> Responsible:    freebsd-amd64
 >> State:          open
 >> Quarter:
 >> Keywords:
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Tue Dec 09 04:30:01 UTC 2008
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     Ven
 >> Release:        6.3-RELEASE-amd64
 >> Organization:
 > Su2
 >> Environment:
 > FreeBSD aop.su-fun.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Aug 27 18:52:34 CST 2008     root@aop.su-fun.com:/usr/obj/usr/src/sys/aop  amd64
 >
 >> Description:
 > system always reboot while quit apache activemq (http://activemq.apache.org/index.html)
 >
 > same problem with diablo-jdk-freebsd6.amd64.1.5.0.07.01 and jdk 1.6.
 >
 >
 >> How-To-Repeat:
 > $ cd /usr/local/activemq/bin
 > $ ./activemq
 >
 > << press Ctrl+C to quit >>
 > .. then system reboot ...
 >> Fix:
 
 Hi Ven,
 
 This might be related to 
 http://security.freebsd.org/advisories/FreeBSD-SA-08:07.amd64.asc .  I 
 originally discovered the bug when running Java (a Linux binary in that 
 case) caused the machine to reboot.  Could you please apply the patch 
 http://security.FreeBSD.org/patches/SA-08:07/amd64.patch , or else upgrade 
 to FreeBSD 6.3-RELEASE-p6 or 6.4-RELEASE, and see if the problem still 
 appears?
 
 -- 
 
 Nate Eldredge
 neldredge@math.ucsd.edu
From neldredge at math.ucsd.edu  Tue Dec  9 02:10:04 2008
From: neldredge at math.ucsd.edu (Nate Eldredge)
Date: Tue Dec  9 02:10:10 2008
Subject: amd64/129515: apache activemq always cause system reboot
Message-ID: <200812091010.mB9AA356095565@freefall.freebsd.org>

The following reply was made to PR amd64/129515; it has been noted by GNATS.

From: Nate Eldredge <neldredge@math.ucsd.edu>
To: YUHONG <bsditer@gmail.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: amd64/129515: apache activemq always cause system reboot
Date: Tue, 9 Dec 2008 02:08:59 -0800 (PST)

 On Tue, 9 Dec 2008, YUHONG wrote:
 
 > hi, Nate Eldredge:
 >
 > 	the issue disappeared after i upgrade to 6.4-RELEASE.
 
 Excellent!
 
 I take it this PR can be closed.
 
 -- 
 
 Nate Eldredge
 neldredge@math.ucsd.edu
From victor at bsdes.net  Tue Dec  9 11:11:08 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Tue Dec  9 11:16:23 2008
Subject: [ATA] and re(4) stability issues
Message-ID: <20081209185236.GA1320@alf.bsdes.net>

Hello,

I got various machines[1] at hetzner.de and I've been having problems
with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
been trying to narrow the problem so someone more knowledgeable than me
is able to fix it. This mail is an other attempt to ask a question
with regards ATA code to see if this time i got something.

For the ones that don't actually know what happened:

With FreeBSD 7.0 -RELEASE for amd64 and default kernel
the system shared re0 interrupt with OHCI and this caused
re(4) to corrupt packets and create interrupt storms. Tried
updating to 7.1 -BETA2 and still had some problems with it.

I've opened the PR kern/128287[2] and Remko quickly answered
with a workaround: that workaround was removing USB support from
my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
and the interrupt storms were gone. Now sometime later the interface
goes up and down from time to time, but less often. Also sometimes
the machine losts the network interface but continues to work.

I know it continues to work because some days later i can see that
it tried to deliver the status reports but was unable to resolve the
aliases hostnames. I can't ping the machine and i know the network
is OK. If i reboot the machine everything is working again.

When switched from 7.0 to 7.1 BETA2 i also found that under load
after some hours the machine created interrupt storms on ATA disks.

Digging at linux source code i've found that they do some special things
for this chipset that i've been unable to find on our code. This is
linux code for my chipset:

371                 AHCI_HFLAGS     (AHCI_HFLAG_IGN_SERR_INTERNAL |
372                                  AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI |
373                                  AHCI_HFLAG_SECT255),

File and the rest of the code in here[3].

As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could
think of, switching MSI and MSI-x off for the whole system, so
i added to /boot/loader.conf this tunables:

hw.pci.enable_msix="0"
hw.pci.enable_msi="0"

And then rebooted the machine. After various hours of doing almost nothing
i've found that the machine answered ping but was unable to answer any
request (eg, ssh, nagios nrpe, etc). The machine recovered itself after
some minutes and when i was able to ssh into i saw the following in dmesg:

ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1463123158

and a lot more errors like that. I didn't get this errors with MSI enabled.
I see WRITE_DMA48 and in linux code i saw AHCI_HFLAG_32BIT_ONLY which is later
used for DMA related things. Could someone who is more knowledgeable check
if we're doing the right thing?

I've attached verbose dmesg of a machine that's like this one with
7.1 -BETA2, MSI enabled and GENERIC kernel minus USB and firewrire.

Also, please, could someone give me a hand on how could i continue debugging
this interrupt issues? I'm a bit lost and digging code and posting each
time i think i've found something is not going to go anywhere.

I would also like to say that i've seen reports of this kind of problems
on amd64 machines in the lists since various years ago, so i don't think
this is just a problem with this BIOS/motherboard (MSI K9AG Neo2 Digital)
on the lists


Thanks in advance for any help.
Regards.


[1]: http://www.hetzner.de/hosting/produkte_rootserver/ds7000/
[2]: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287
[3]: http://fxr.watson.org/fxr/source/drivers/ata/ahci.c?v=linux-2.6#L369
-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
-------------- next part --------------
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-BETA2 #1: Wed Oct 22 13:19:14 CEST 2008
    victor@foo.bar.com:/usr/obj/usr/src/sys/NOUSB
Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80c12000.
Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80c121a8.
Preloaded elf obj module "/boot/kernel/accf_data.ko" at 0xffffffff80c12818.
Preloaded elf obj module "/boot/kernel/accf_http.ko" at 0xffffffff80c12cc8.
Preloaded elf obj module "/boot/kernel/k8temp.ko" at 0xffffffff80c13238.
Preloaded elf obj module "/boot/kernel/geom_journal.ko" at 0xffffffff80c13720.
Calibrating clock(s) ... i8254 clock: 1193242 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2999975813 Hz
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.98-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x40f33  Stepping = 3
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8>
  Cores per package: 2
L1 2MB data TLB: 8 entries, fully associative
L1 2MB instruction TLB: 8 entries, fully associative
L1 4KB data TLB: 32 entries, fully associative
L1 4KB instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 2MB unified TLB: 0 entries, disabled/not present
L2 4KB data TLB: 512 entries, 4-way associative
L2 4KB instruction TLB: 512 entries, 4-way associative
L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative
usable memory = 6395625472 (6099 MB)
Physical memory chunk(s):
0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages)
0x0000000000d13000 - 0x00000000d1c6bfff, 3505754112 bytes (855897 pages)
0x0000000100000000 - 0x000000019ffeffff, 2684289024 bytes (655344 pages)
avail memory  = 6179069952 (5892 MB)
ACPI APIC Table: <M S I  OEMAPIC >
INTR: Adding local APIC 1 as a target
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 2
ULE: setup cpu group 0
ULE: setup cpu 0
ULE: adding cpu 0 to group 0: cpus 1 mask 0x1
ULE: setup cpu group 1
ULE: setup cpu 1
ULE: adding cpu 1 to group 1: cpus 1 mask 0x2
ACPI: RSDP @ 0x0xf98a0/0x0014 (v  0 ACPIAM)
ACPI: RSDT @ 0x0xddfd0000/0x003C (v  1 M S I  OEMRSDT  0x10000731 MSFT 0x00000097)
ACPI: FACP @ 0x0xddfd0200/0x0084 (v  2 M S I  OEMFACP  0x10000731 MSFT 0x00000097)
ACPI: DSDT @ 0x0xddfd0430/0x40D9 (v  1  1ADNC 1ADNC000 0x00000000 INTL 0x20051117)
ACPI: FACS @ 0x0xddfde000/0x0040
ACPI: APIC @ 0x0xddfd0390/0x005C (v  1 M S I  OEMAPIC  0x10000731 MSFT 0x00000097)
ACPI: MCFG @ 0x0xddfd03f0/0x003C (v  1 M S I  OEMMCFG  0x10000731 MSFT 0x00000097)
ACPI: OEMB @ 0x0xddfde040/0x0060 (v  1 M S I  AMI_OEM  0x10000731 MSFT 0x00000097)
ACPI: EPTH @ 0x0xddfd4510/0x0038 (v  1 M S I  OEMHPET  0x10000731 MSFT 0x00000097)
ACPI: SSDT @ 0x0xddfd4550/0x030E (v  1 A M I  POWERNOW 0x00000001 AMD  0x00000001)
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000
ioapic0: Routing external 8259A's -> intpin 0
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
MADT: Interrupt override: source 9, irq 9
ioapic0: intpin 9 trigger: level
ioapic0: intpin 9 polarity: low
ioapic0 <Version 2.1> irqs 0-23 on motherboard
cpu0 BSP:
     ID: 0x00000000   VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
  lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
  timer: 0x000100ef therm: 0x00010000 err: 0x0001000f pcm: 0x00010000
wlan: <802.11 Link Layer>
ath_rate: version 1.2 <SampleRate bit-rate selection algorithm>
wlan_amrr: <AMRR Transmit Rate Control Algorithm>
nfslock: pseudo-device
kbd: new array size 4
kbd1 at kbdmux0
mem: <memory>
null: <null device, zero device>
io: <I/O>
random: <entropy source, Software, Yarrow>
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Oct 22 2008 13:19:08)
acpi0: <M S I OEMRSDT> on motherboard
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
AcpiOsDerivePciId: \\_SB_.PCI0.RS48.NB2_ -> bus 0 dev 0 func 0
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, ddf00000 (3) failed
ACPI timer: 0/838 0/839 0/841 0/895 0/842 0/840 0/837 0/890 0/836 0/837 -> 0
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pci_link0:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0    5   N     0  3 4 5 7 10 11 12 14 15
  Validation          0    5   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link1:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0    7   N     0  3 4 5 7 10 11 12 14 15
  Validation          0    7   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link2:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0   10   N     0  3 4 5 7 10 11 12 14 15
  Validation          0   10   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link3:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0   10   N     0  3 4 5 7 10 11 12 14 15
  Validation          0   10   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link4:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0    4   N     0  3 4 5 7 10 11 12 14 15
  Validation          0    4   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link5:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  3 4 5 7 10 11 12 14 15
  Validation          0  255   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link6:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0   11   N     0  3 4 5 7 10 11 12 14 15
  Validation          0   11   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pci_link7:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  3 4 5 7 10 11 12 14 15
  Validation          0  255   N     0  3 4 5 7 10 11 12 14 15
  After Disable       0  255   N     0  3 4 5 7 10 11 12 14 15
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: domain=0, physical bus=0
found->	vendor=0x1002, dev=0x7910, revid=0x00
	domain=0, bus=0, slot=0, func=0
	class=06-00-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x2220, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x7912, revid=0x00
	domain=0, bus=0, slot=1, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
	cmdreg=0x0107, statreg=0x0230, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x1a (6500 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x7917, revid=0x00
	domain=0, bus=0, slot=7, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
	cmdreg=0x0107, statreg=0x4010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns)
	powerspec 3  supports D0 D3  current D0
	MSI supports 1 message
found->	vendor=0x1002, dev=0x4380, revid=0x00
	domain=0, bus=0, slot=18, func=0
	class=01-01-8f, hdrtype=0x00, mfdev=0
	cmdreg=0x0107, statreg=0x0230, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=11
	powerspec 2  supports D0 D3  current D0
	map[10]: type I/O Port, range 32, base 0xb000, size  3, enabled
	map[14]: type I/O Port, range 32, base 0xa000, size  2, enabled
	map[18]: type I/O Port, range 32, base 0x9000, size  3, enabled
	map[1c]: type I/O Port, range 32, base 0x8000, size  2, enabled
	map[20]: type I/O Port, range 32, base 0x7000, size  4, enabled
	map[24]: type Memory, range 32, base 0xfe7ff800, size 10, enabled
pcib0: matched entry for 0.18.INTA
pcib0: slot 18 INTA hardwired to IRQ 22
found->	vendor=0x1002, dev=0x4387, revid=0x00
	domain=0, bus=0, slot=19, func=0
	class=0c-03-10, hdrtype=0x00, mfdev=1
	cmdreg=0x0517, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=5
	map[10]: type Memory, range 32, base 0xfe7fe000, size 12, enabled
pcib0: matched entry for 0.19.INTA
pcib0: slot 19 INTA hardwired to IRQ 16
found->	vendor=0x1002, dev=0x4388, revid=0x00
	domain=0, bus=0, slot=19, func=1
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0517, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=7
	map[10]: type Memory, range 32, base 0xfe7fd000, size 12, enabled
pcib0: matched entry for 0.19.INTB
pcib0: slot 19 INTB hardwired to IRQ 17
found->	vendor=0x1002, dev=0x4389, revid=0x00
	domain=0, bus=0, slot=19, func=2
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=c, irq=10
	map[10]: type Memory, range 32, base 0xfe7fc000, size 12, enabled
pcib0: matched entry for 0.19.INTC
pcib0: slot 19 INTC hardwired to IRQ 18
found->	vendor=0x1002, dev=0x438a, revid=0x00
	domain=0, bus=0, slot=19, func=3
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=7
	map[10]: type Memory, range 32, base 0xfe7fb000, size 12, enabled
pcib0: matched entry for 0.19.INTB
pcib0: slot 19 INTB hardwired to IRQ 17
found->	vendor=0x1002, dev=0x438b, revid=0x00
	domain=0, bus=0, slot=19, func=4
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=c, irq=10
	map[10]: type Memory, range 32, base 0xfe7fa000, size 12, enabled
pcib0: matched entry for 0.19.INTC
pcib0: slot 19 INTC hardwired to IRQ 18
found->	vendor=0x1002, dev=0x4386, revid=0x00
	domain=0, bus=0, slot=19, func=5
	class=0c-03-20, hdrtype=0x00, mfdev=0
	cmdreg=0x0517, statreg=0x02b0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=d, irq=10
	powerspec 2  supports D0 D1 D2 D3  current D0
	map[10]: type Memory, range 32, base 0xfe7ff000, size  8, enabled
pcib0: matched entry for 0.19.INTD
pcib0: slot 19 INTD hardwired to IRQ 19
found->	vendor=0x1002, dev=0x4385, revid=0x14
	domain=0, bus=0, slot=20, func=0
	class=0c-05-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0401, statreg=0x0230, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	map[10]: type I/O Port, range 32, base 0xb00, size  4, enabled
found->	vendor=0x1002, dev=0x438c, revid=0x00
	domain=0, bus=0, slot=20, func=1
	class=01-01-8a, hdrtype=0x00, mfdev=0
	cmdreg=0x0005, statreg=0x0220, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=255
	map[20]: type I/O Port, range 32, base 0xff00, size  4, enabled
found->	vendor=0x1002, dev=0x438d, revid=0x00
	domain=0, bus=0, slot=20, func=3
	class=06-01-00, hdrtype=0x00, mfdev=1
	cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x4384, revid=0x00
	domain=0, bus=0, slot=20, func=4
	class=06-04-01, hdrtype=0x01, mfdev=1
	cmdreg=0x0107, statreg=0x02a0, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1100, revid=0x00
	domain=0, bus=0, slot=24, func=0
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1101, revid=0x00
	domain=0, bus=0, slot=24, func=1
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1102, revid=0x00
	domain=0, bus=0, slot=24, func=2
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1103, revid=0x00
	domain=0, bus=0, slot=24, func=3
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pcib1:   domain            0
pcib1:   secondary bus     1
pcib1:   subordinate bus   1
pcib1:   I/O decode        0xc000-0xcfff
pcib1:   memory decode     0xfe800000-0xfe9fffff
pcib1:   prefetched decode 0xfc000000-0xfdffffff
pci1: <ACPI PCI bus> on pcib1
pci1: domain=0, physical bus=1
found->	vendor=0x1002, dev=0x791e, revid=0x00
	domain=0, bus=1, slot=5, func=0
	class=03-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 2  supports D0 D1 D2 D3  current D0
	MSI supports 1 message, 64 bit
	map[10]: type Prefetchable Memory, range 64, base 0xfc000000, size 25, enabled
pcib1: requested memory range 0xfc000000-0xfdffffff: good
	map[18]: type Memory, range 64, base 0xfe9f0000, size 16, enabled
pcib1: requested memory range 0xfe9f0000-0xfe9fffff: good
	map[20]: type I/O Port, range 32, base 0xc000, size  8, enabled
pcib1: requested I/O range 0xc000-0xc0ff: in range
	map[24]: type Memory, range 32, base 0xfe800000, size 20, enabled
pcib1: requested memory range 0xfe800000-0xfe8fffff: good
pcib1: matched entry for 1.5.INTA
pcib1: slot 5 INTA hardwired to IRQ 18
found->	vendor=0x1002, dev=0x7919, revid=0x00
	domain=0, bus=1, slot=5, func=2
	class=04-03-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=10
	powerspec 2  supports D0 D3  current D0
	MSI supports 1 message, 64 bit
	map[10]: type Memory, range 64, base 0xfe9e8000, size 14, enabled
pcib1: requested memory range 0xfe9e8000-0xfe9ebfff: good
pcib1: matched entry for 1.5.INTB
pcib1: slot 5 INTB hardwired to IRQ 19
vgapci0: <VGA-compatible display> port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1
pci1: <multimedia> at device 5.2 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pcib2:   domain            0
pcib2:   secondary bus     2
pcib2:   subordinate bus   2
pcib2:   I/O decode        0xd000-0xdfff
pcib2:   memory decode     0xfea00000-0xfeafffff
pcib2:   no prefetched decode
pci2: <ACPI PCI bus> on pcib2
pci2: domain=0, physical bus=2
found->	vendor=0x10ec, dev=0x8168, revid=0x01
	domain=0, bus=2, slot=0, func=0
	class=02-00-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x4010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 2  supports D0 D1 D2 D3  current D0
	MSI supports 2 messages, 64 bit
	map[10]: type I/O Port, range 32, base 0xd800, size  8, enabled
pcib2: requested I/O range 0xd800-0xd8ff: in range
	map[18]: type Memory, range 64, base 0xfeaff000, size 12, enabled
pcib2: requested memory range 0xfeaff000-0xfeafffff: good
pcib2: matched entry for 2.0.INTA
pcib2: slot 0 INTA hardwired to IRQ 19
re0: <RealTek 8168/8168B/8168C/8168CP/8111B/8111C/8111CP PCIe Gigabit Ethernet> port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2
re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xfeaff000
re0: MSI count : 2
re0: turning off MSI enable bit.
re0: Chip rev. 0x38000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
re0: bpf attached
re0: Ethernet address: 00:21:85:15:30:14
ioapic0: routing intpin 19 (PCI IRQ 19) to vector 49
re0: [MPSAFE]
re0: [FILTER]
atapci0: <ATI IXP600 SATA300 controller> port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0
atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x7000
atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfe7ff800
ioapic0: routing intpin 22 (PCI IRQ 22) to vector 50
atapci0: [MPSAFE]
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci0
ata2: SATA connect time=0ms
ata2: SIGNATURE: 00000101
ata2: ahci_reset devices=0x1<ATA_MASTER>
ata2: [MPSAFE]
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: SATA connect time=0ms
ata3: SIGNATURE: 00000101
ata3: ahci_reset devices=0x1<ATA_MASTER>
ata3: [MPSAFE]
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: SATA connect status=00000000
ata4: ahci_reset devices=0x0
ata4: [MPSAFE]
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: SATA connect status=00000000
ata5: ahci_reset devices=0x0
ata5: [MPSAFE]
ata5: [ITHREAD]
pci0: <serial bus, USB> at device 19.0 (no driver attached)
pci0: <serial bus, USB> at device 19.1 (no driver attached)
pci0: <serial bus, USB> at device 19.2 (no driver attached)
pci0: <serial bus, USB> at device 19.3 (no driver attached)
pci0: <serial bus, USB> at device 19.4 (no driver attached)
pci0: <serial bus, USB> at device 19.5 (no driver attached)
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xff00
ata0: <ATA channel 0> on atapci1
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
ata0: reset tp1 mask=00 ostat0=ff ostat1=ff
ioapic0: routing intpin 14 (ISA IRQ 14) to vector 51
ata0: [MPSAFE]
ata0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib3: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pcib3:   domain            0
pcib3:   secondary bus     3
pcib3:   subordinate bus   3
pcib3:   I/O decode        0xe000-0xefff
pcib3:   memory decode     0xfeb00000-0xfebfffff
pcib3:   no prefetched decode
pcib3:   Subtractively decoded bridge.
pci3: <ACPI PCI bus> on pcib3
pci3: domain=0, physical bus=3
k8temp0: <AMD K8 Thermal Sensors> on hostb4
acpi_button0: <Power Button> on acpi0
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: irq maps: 0 0 0 0
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: irq maps: 0 0 0 0
sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0
sio0: type 16550A
ioapic0: routing intpin 3 (ISA IRQ 3) to vector 52
sio0: [FILTER]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0065
atkbd: keyboard ID 0x41ab (2)
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
ioapic0: routing intpin 1 (ISA IRQ 1) to vector 53
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: unable to allocate IRQ
cpu0: <ACPI CPU> on acpi0
cpu0: switching to generic Cx mode
acpi_throttle0: <ACPI CPU Throttling> on cpu0
acpi_throttle0: CLK_VAL field overlaps THT_EN bit
device_attach: acpi_throttle0 attach returned 6
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <PowerNow! K8> on cpu1
ex_isa_identify()
atkbdc: atkbdc0 already exists; skipping it
sio: sio0 already exists; skipping it
ahc_isa_probe 0: ioport 0xc00 alloc failed
sc: sc0 already exists; skipping it
vga: vga0 already exists; skipping it
isa_probe_children: disabling PnP devices
isa_probe_children: probing non-PnP devices
orm0: <ISA Option ROM> at iomem 0xcd800-0xce7ff on isa0
fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
ppc0: cannot reserve I/O port range
ppc0: <Parallel port> failed to probe at irq 7 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd1, terminal emulator: sc (syscons terminal)
sio1 failed to probe at port 0x2f8 irq 3 on isa0
sio2: not probed (disabled)
sio3: not probed (disabled)
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
isa_probe_children: probing PnP devices
Device configuration finished.
Reducing kern.maxvnodes 235635 -> 100000
procfs registered
lapic: Divisor 2, Frequency 99999202 hz
Timecounter "TSC" frequency 2999975813 Hz quality -100
Timecounters tick every 1.000 msec
lo0: bpf attached
hptrr: no controller detected.
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad4: 715404MB <SAMSUNG HD753LJ 1AA01113> at ata2-master SATA300
ad4: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue
GEOM: new disk ad4
ad4: Silicon Image check1 failed
ad4: Adaptec check1 failed
ad4: LSI (v3) check1 failed
ad4: LSI (v2) check1 failed
ad4: FreeBSD check1 failed
ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire
ad6: 715404MB <SAMSUNG HD753LJ 1AA01112> at ata3-master SATA300
ad6: 1465149168 sectors [1453521C/16H/63S] 16 sectors/interrupt 1 depth queue
GEOM: new disk ad6
ad6: Silicon Image check1 failed
ad6: Adaptec check1 failed
ad6: LSI (v3) check1 failed
ad6: LSI (v2) check1 failed
ad6: FreeBSD check1 failed
ATA PseudoRAID loaded
SMP: AP CPU #1 Launched!
cpu1 AP:
     ID: 0x01000000   VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
  lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
  timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000
ioapic0: Assigning ISA IRQ 1 to local APIC 0
ioapic0: Assigning ISA IRQ 3 to local APIC 1
ioapic0: Assigning ISA IRQ 9 to local APIC 0
ioapic0: Assigning ISA IRQ 14 to local APIC 1
ioapic0: Assigning PCI IRQ 19 to local APIC 0
ioapic0: Assigning PCI IRQ 22 to local APIC 1
GEOM_MIRROR: Device mirror/os launched (2/2).
GEOM_JOURNAL: Journal 647493113: mirror/oss1g contains data.
GEOM_JOURNAL: Journal 647493113: mirror/oss1g contains journal.
GEOM_JOURNAL: Journal mirror/oss1g clean.
Trying to mount root from ufs:/dev/mirror/oss1a
start_init: trying /sbin/init
re0: link state changed to UP
From pyunyh at gmail.com  Tue Dec  9 22:36:49 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Tue Dec  9 22:36:56 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081209185236.GA1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
Message-ID: <20081210061226.GC37837@cdnetworks.co.kr>

On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
 > Hello,
 > 
 > I got various machines[1] at hetzner.de and I've been having problems
 > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
 > been trying to narrow the problem so someone more knowledgeable than me
 > is able to fix it. This mail is an other attempt to ask a question
 > with regards ATA code to see if this time i got something.
 > 
 > For the ones that don't actually know what happened:
 > 
 > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
 > the system shared re0 interrupt with OHCI and this caused
 > re(4) to corrupt packets and create interrupt storms. Tried

re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
triggered on systems with > 4GB memory. But I dont' know whether
this is related with interrupt storms.

 > updating to 7.1 -BETA2 and still had some problems with it.
 > 
 > I've opened the PR kern/128287[2] and Remko quickly answered
 > with a workaround: that workaround was removing USB support from
 > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
 > and the interrupt storms were gone. Now sometime later the interface
 > goes up and down from time to time, but less often. Also sometimes
 > the machine losts the network interface but continues to work.
 > 

It seems that your controller supports MSI so you can set a tunable
hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
interrupt sharing(e.g. add hw.re.msi_disable="0" to
/boot/loader.conf file.) However there were several issues on re(4)
w.r.t MSI so it was off by default.

 > I know it continues to work because some days later i can see that
 > it tried to deliver the status reports but was unable to resolve the
 > aliases hostnames. I can't ping the machine and i know the network
 > is OK. If i reboot the machine everything is working again.
 > 

Recently I've made small changes to re(4) which may help to detect
link state change event. Would you try re(4) in HEAD?

-- 
Regards,
Pyun YongHyeon
From pyunyh at gmail.com  Wed Dec 10 02:28:15 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Dec 10 02:28:29 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210085934.GB1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
Message-ID: <20081210102800.GH37837@cdnetworks.co.kr>

On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote:
 > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote:
 > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
 > >  > Hello,
 > >  > 
 > >  > I got various machines[1] at hetzner.de and I've been having problems
 > >  > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
 > >  > been trying to narrow the problem so someone more knowledgeable than me
 > >  > is able to fix it. This mail is an other attempt to ask a question
 > >  > with regards ATA code to see if this time i got something.
 > >  > 
 > >  > For the ones that don't actually know what happened:
 > >  > 
 > >  > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
 > >  > the system shared re0 interrupt with OHCI and this caused
 > >  > re(4) to corrupt packets and create interrupt storms. Tried
 > > 
 > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
 > > triggered on systems with > 4GB memory. But I dont' know whether
 > > this is related with interrupt storms.
 > > 
 > >  > updating to 7.1 -BETA2 and still had some problems with it.
 > >  > 
 > >  > I've opened the PR kern/128287[2] and Remko quickly answered
 > >  > with a workaround: that workaround was removing USB support from
 > >  > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
 > >  > and the interrupt storms were gone. Now sometime later the interface
 > >  > goes up and down from time to time, but less often. Also sometimes
 > >  > the machine losts the network interface but continues to work.
 > >  > 
 > > 
 > > It seems that your controller supports MSI so you can set a tunable
 > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
 > > interrupt sharing(e.g. add hw.re.msi_disable="0" to
 > > /boot/loader.conf file.) However there were several issues on re(4)
 > > w.r.t MSI so it was off by default.
 > 
 > This is undocumented and with sysctl -a i can't find the tunable. Is this
 > a HEAD feature or it's also in 7.1 -BETA2? Should i add

Yeah it's an undocmented feature. But most drivers written by me
have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have
the tunable.

 > hw.re_msi_disable="0" to /boot/loader.conf?
   ^^^^^^^^^^^^^^^^^^^^^
   Shoule be hw.re.msi_disable="0"
 > 

Yes, just add it to /boot/loader.conf. Note, you should not disable
system-wide MSI control(e.g. hw.pci.enable_msi == 1).

 > This was sharing interrupt with USB, does USB need any special MSI handling
 > or with re using MSI is enough to not share the interrupt?

If re(4) can use MSI, you don't need to worry about interrupt
sharing with USB. Check the output of "vmstat -i". You normally get
an irq256 or higher for MSI enabled driver.

 > 
 > 
 > > 
 > >  > I know it continues to work because some days later i can see that
 > >  > it tried to deliver the status reports but was unable to resolve the
 > >  > aliases hostnames. I can't ping the machine and i know the network
 > >  > is OK. If i reboot the machine everything is working again.
 > >  > 
 > > 
 > > Recently I've made small changes to re(4) which may help to detect
 > > link state change event. Would you try re(4) in HEAD?
 > 
 > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that

Yes, you can. It should build without problems. Just replace re(4) on
stable/7 with HEAD version.

 > or do i need to test the whole HEAD kernel?
 > 

No you don't have to that.

-- 
Regards,
Pyun YongHyeon
From pyunyh at gmail.com  Wed Dec 10 04:07:29 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Dec 10 04:07:35 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210113225.GD1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
Message-ID: <20081210120719.GK37837@cdnetworks.co.kr>

On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
 > On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote:
 > > On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote:
 > >  > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote:
 > >  > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
 > >  > >  > Hello,
 > >  > >  > 
 > >  > >  > I got various machines[1] at hetzner.de and I've been having problems
 > >  > >  > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
 > >  > >  > been trying to narrow the problem so someone more knowledgeable than me
 > >  > >  > is able to fix it. This mail is an other attempt to ask a question
 > >  > >  > with regards ATA code to see if this time i got something.
 > >  > >  > 
 > >  > >  > For the ones that don't actually know what happened:
 > >  > >  > 
 > >  > >  > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
 > >  > >  > the system shared re0 interrupt with OHCI and this caused
 > >  > >  > re(4) to corrupt packets and create interrupt storms. Tried
 > >  > > 
 > >  > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
 > >  > > triggered on systems with > 4GB memory. But I dont' know whether
 > >  > > this is related with interrupt storms.
 > >  > > 
 > >  > >  > updating to 7.1 -BETA2 and still had some problems with it.
 > >  > >  > 
 > >  > >  > I've opened the PR kern/128287[2] and Remko quickly answered
 > >  > >  > with a workaround: that workaround was removing USB support from
 > >  > >  > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
 > >  > >  > and the interrupt storms were gone. Now sometime later the interface
 > >  > >  > goes up and down from time to time, but less often. Also sometimes
 > >  > >  > the machine losts the network interface but continues to work.
 > >  > >  > 
 > >  > > 
 > >  > > It seems that your controller supports MSI so you can set a tunable
 > >  > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
 > >  > > interrupt sharing(e.g. add hw.re.msi_disable="0" to
 > >  > > /boot/loader.conf file.) However there were several issues on re(4)
 > >  > > w.r.t MSI so it was off by default.
 > >  > 
 > >  > This is undocumented and with sysctl -a i can't find the tunable. Is this
 > >  > a HEAD feature or it's also in 7.1 -BETA2? Should i add
 > > 
 > > Yeah it's an undocmented feature. But most drivers written by me
 > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have
 > > the tunable.
 > 
 > I think it could be great if you could document it or at least
 > show it by default when you do sysctl -ad with a small description.
 > 

If MSI worked as expected I would have documented it as I did
in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc.
Using MSI on RealTek does not seem to stable. I tried hard to fix
that but some users still reported watchdog timeouts. Working
without documentation and hardware also made it hard to complete
the work. This was the main reason why MSI was disabled on re(4).

 > > 
 > >  > hw.re_msi_disable="0" to /boot/loader.conf?
 > >    ^^^^^^^^^^^^^^^^^^^^^
 > >    Shoule be hw.re.msi_disable="0"
 > >  > 
 > > 
 > > Yes, just add it to /boot/loader.conf. Note, you should not disable
 > > system-wide MSI control(e.g. hw.pci.enable_msi == 1).
 > > 
 > >  > This was sharing interrupt with USB, does USB need any special MSI handling
 > >  > or with re using MSI is enough to not share the interrupt?
 > > 
 > > If re(4) can use MSI, you don't need to worry about interrupt
 > > sharing with USB. Check the output of "vmstat -i". You normally get
 > > an irq256 or higher for MSI enabled driver.
 > > 
 > >  > 
 > >  > 
 > >  > > 
 > >  > >  > I know it continues to work because some days later i can see that
 > >  > >  > it tried to deliver the status reports but was unable to resolve the
 > >  > >  > aliases hostnames. I can't ping the machine and i know the network
 > >  > >  > is OK. If i reboot the machine everything is working again.
 > >  > >  > 
 > >  > > 
 > >  > > Recently I've made small changes to re(4) which may help to detect
 > >  > > link state change event. Would you try re(4) in HEAD?
 > >  > 
 > >  > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that
 > > 
 > > Yes, you can. It should build without problems. Just replace re(4) on
 > > stable/7 with HEAD version.
 > > 
 > >  > or do i need to test the whole HEAD kernel?
 > >  > 
 > > 
 > > No you don't have to that.
 > 
 > Backporting the changes i've found that it didn't compile so in
 > the end i got from HEAD the following files:
 > 
 > base/head/sys/dev/re/if_re.c
 > base/head/sys/pci/if_rl.c
 > base/head/sys/pci/if_rlreg.h
 > 

Ah,, sorry about that. Recently there was some changes. I forgot
that.

 > After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled
 > the knob you suggested in /boot/loader.conf.
 > 
 > With the new kernel and MSI the interrupts are like this:
 > 
 > # vmstat -i
 > interrupt                          total       rate
 > irq9: acpi0                            1          0
 > irq16: ohci0                           1          0
 > irq17: ohci1 ohci3                     1          0
 > irq18: ohci2 ohci4                     1          0
 > irq22: atapci0                     19215         15
 > cpu0: timer                      2502718       1998
 > irq256: re0                      4967726       3967
 > cpu1: timer                      2502525       1998
 > Total                            9992188       7980
 > 
 > The high interrupt numbers are because i've been running iperf to
 > check everything it's fine, not because of interrupt storms. So far
 > i didn't find any interrupt storms related to USB or re(4) driver
 > but while doing the tests i've found this error:
 > 
 > re0: watchdog timeout (missed Tx interrupts) -- recovering
 > 
 > This didn't create any error on the interfaces (netstat -i).
 > 

This was triggered by new code in HEAD. It indicates re(4) missed
Tx completion interrupt. It could be a bug in driver or hardware
bug. If you can live with that message you can safely ignore that
as now re(4) does not reinitialize the hardware if it detect
missing Tx completion interrupt.

 > Also i didn't see any problem with interfaces going up and down,
 > but that usually happen after some hours of uptime, so i'll let
 > you know if the error happens again.
 > 

Ok.

 > As these seems to improve the current situation, is there any
 > chance of merging -current driver in 7.1 before release?
 > 

I think re(4) in HEAD needs more testing. As you might know RealTek
produced too many chipsets. :-(

-- 
Regards,
Pyun YongHyeon
From gary.jennejohn at freenet.de  Wed Dec 10 06:02:14 2008
From: gary.jennejohn at freenet.de (Gary Jennejohn)
Date: Wed Dec 10 06:02:21 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
Message-ID: <20081210150207.4951a157@ernst.jennejohn.org>

On Wed, 10 Dec 2008 21:07:19 +0900
Pyun YongHyeon <pyunyh@gmail.com> wrote:
> On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:

>  > As these seems to improve the current situation, is there any
>  > chance of merging -current driver in 7.1 before release?
>  >
>
> I think re(4) in HEAD needs more testing. As you might know RealTek
> produced too many chipsets. :-(
>

FYI I've now turned MSI on in HEAD and will see what happens.  Before
my re0 was sharing interrupts with 3 USB controllers.  Now it's all
by itself on irq256.

I'm running amd64 with

re0: <RealTek 8168/8168B/8168C/8168CP/8168D/8111B/8111C/8111CP PCIe
Gigabit Ethernet> port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff,
0xfdae0000-0xfdaeffff irq 18 at device 0.0 on pci2

---
Gary Jennejohn
From victor at bsdes.net  Wed Dec 10 00:59:38 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:09:30 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210061226.GC37837@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
Message-ID: <20081210085934.GB1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote:
> On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
>  > Hello,
>  > 
>  > I got various machines[1] at hetzner.de and I've been having problems
>  > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
>  > been trying to narrow the problem so someone more knowledgeable than me
>  > is able to fix it. This mail is an other attempt to ask a question
>  > with regards ATA code to see if this time i got something.
>  > 
>  > For the ones that don't actually know what happened:
>  > 
>  > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
>  > the system shared re0 interrupt with OHCI and this caused
>  > re(4) to corrupt packets and create interrupt storms. Tried
> 
> re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
> triggered on systems with > 4GB memory. But I dont' know whether
> this is related with interrupt storms.
> 
>  > updating to 7.1 -BETA2 and still had some problems with it.
>  > 
>  > I've opened the PR kern/128287[2] and Remko quickly answered
>  > with a workaround: that workaround was removing USB support from
>  > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
>  > and the interrupt storms were gone. Now sometime later the interface
>  > goes up and down from time to time, but less often. Also sometimes
>  > the machine losts the network interface but continues to work.
>  > 
> 
> It seems that your controller supports MSI so you can set a tunable
> hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
> interrupt sharing(e.g. add hw.re.msi_disable="0" to
> /boot/loader.conf file.) However there were several issues on re(4)
> w.r.t MSI so it was off by default.

This is undocumented and with sysctl -a i can't find the tunable. Is this
a HEAD feature or it's also in 7.1 -BETA2? Should i add
hw.re_msi_disable="0" to /boot/loader.conf?

This was sharing interrupt with USB, does USB need any special MSI handling
or with re using MSI is enough to not share the interrupt?


> 
>  > I know it continues to work because some days later i can see that
>  > it tried to deliver the status reports but was unable to resolve the
>  > aliases hostnames. I can't ping the machine and i know the network
>  > is OK. If i reboot the machine everything is working again.
>  > 
> 
> Recently I've made small changes to re(4) which may help to detect
> link state change event. Would you try re(4) in HEAD?

Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that
or do i need to test the whole HEAD kernel?

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From bu7cher at yandex.ru  Wed Dec 10 01:09:56 2008
From: bu7cher at yandex.ru (Andrey V. Elsukov)
Date: Wed Dec 10 06:09:49 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081209185236.GA1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
Message-ID: <493F84A4.1080308@yandex.ru>

Victor Balada Diaz wrote:
> Digging at linux source code i've found that they do some special things
> for this chipset that i've been unable to find on our code. This is
> linux code for my chipset:
> 
> 371                 AHCI_HFLAGS     (AHCI_HFLAG_IGN_SERR_INTERNAL |
> 372                                  AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI |
> 373                                  AHCI_HFLAG_SECT255),
> 
> File and the rest of the code in here[3].
> 
> As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could
> think of, switching MSI and MSI-x off for the whole system, so
> i added to /boot/loader.conf this tunables:

FreeBSD's ata(4) driver doesn't support MSI. This flag in linux's libata used in

     if ((hpriv->flags & AHCI_HFLAG_NO_MSI) || pci_enable_msi(pdev))
                 pci_intx(pdev, 1);

In FreeBSD's code we have the same:

     /* enable PCI interrupt */
     pci_write_config(dev, PCIR_COMMAND,
                      pci_read_config(dev, PCIR_COMMAND, 2) & ~0x0400, 2);

AHCI_HFLAG_IGN_SERR_INTERNAL flag targeted to ignore SERR_INTERNAL errors.
FreeBSD's ata(4) driver ignores they too.

AHCI_HFLAG_32BIT_ONLY flag limits to use 32-bit DMA only.
If AHCI CAP register reports that controller supports 64-bit DMA driver will use 64-bit.
So i think there can be added one quirk for you, but i'm not sure that problem is here..

AHCI_HFLAG_SECT255 flag limits I/O operation to 255 sectors, FreeBSD uses 128-limit
by default.

-- 
WBR, Andrey V. Elsukov

From victor at bsdes.net  Wed Dec 10 01:11:09 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:10:01 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <493F84A4.1080308@yandex.ru>
References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru>
Message-ID: <20081210091107.GC1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 11:58:12AM +0300, Andrey V. Elsukov wrote:
> Victor Balada Diaz wrote:
> >Digging at linux source code i've found that they do some special things
> >for this chipset that i've been unable to find on our code. This is
> >linux code for my chipset:
> >
> >371                 AHCI_HFLAGS     (AHCI_HFLAG_IGN_SERR_INTERNAL |
> >372                                  AHCI_HFLAG_32BIT_ONLY | 
> >AHCI_HFLAG_NO_MSI |
> >373                                  AHCI_HFLAG_SECT255),
> >
> >File and the rest of the code in here[3].
> >
> >As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could
> >think of, switching MSI and MSI-x off for the whole system, so
> >i added to /boot/loader.conf this tunables:
> 
> FreeBSD's ata(4) driver doesn't support MSI. This flag in linux's libata 
> used in
> 
>     if ((hpriv->flags & AHCI_HFLAG_NO_MSI) || pci_enable_msi(pdev))
>                 pci_intx(pdev, 1);
> 
> In FreeBSD's code we have the same:
> 
>     /* enable PCI interrupt */
>     pci_write_config(dev, PCIR_COMMAND,
>                      pci_read_config(dev, PCIR_COMMAND, 2) & ~0x0400, 2);
> 
> AHCI_HFLAG_IGN_SERR_INTERNAL flag targeted to ignore SERR_INTERNAL errors.
> FreeBSD's ata(4) driver ignores they too.
> 
> AHCI_HFLAG_32BIT_ONLY flag limits to use 32-bit DMA only.
> If AHCI CAP register reports that controller supports 64-bit DMA driver 
> will use 64-bit.
> So i think there can be added one quirk for you, but i'm not sure that 
> problem is here..
> 
> AHCI_HFLAG_SECT255 flag limits I/O operation to 255 sectors, FreeBSD uses 
> 128-limit
> by default.

Thanks for explaining me what the flags do. I'm not skilled enough to create
the DMA quirks but if you could give me some patches i'll test them. Also
if you have any other idea on what could i test or how can i debug this
it would be more than welcome.

Thanks.
Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From sos at FreeBSD.ORG  Wed Dec 10 01:55:40 2008
From: sos at FreeBSD.ORG (=?ISO-8859-1?Q?S=F8ren_Schmidt?=)
Date: Wed Dec 10 06:10:15 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210091107.GC1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru>
	<20081210091107.GC1320@alf.bsdes.net>
Message-ID: <A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>

On 10Dec, 2008, at 10:11 , Victor Balada Diaz wrote:
>
> Thanks for explaining me what the flags do. I'm not skilled enough  
> to create
> the DMA quirks but if you could give me some patches i'll test them.  
> Also
> if you have any other idea on what could i test or how can i debug  
> this
> it would be more than welcome.


Comment out the following two lines in ata_ahci_dmainit():

         if (ATA_INL(ctlr->r_res2, ATA_AHCI_CAP) & ATA_AHCI_CAP_64BIT)
             ch->dma->max_address = BUS_SPACE_MAXADDR;

And you will not use 64bit DMA even if the chipset supports it.  
However I have not seen any chipsets supporting this fail, YMMV as  
usual :)

-S?ren






From victor at bsdes.net  Wed Dec 10 03:32:28 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:10:26 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210102800.GH37837@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
Message-ID: <20081210113225.GD1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote:
> On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote:
>  > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote:
>  > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
>  > >  > Hello,
>  > >  > 
>  > >  > I got various machines[1] at hetzner.de and I've been having problems
>  > >  > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
>  > >  > been trying to narrow the problem so someone more knowledgeable than me
>  > >  > is able to fix it. This mail is an other attempt to ask a question
>  > >  > with regards ATA code to see if this time i got something.
>  > >  > 
>  > >  > For the ones that don't actually know what happened:
>  > >  > 
>  > >  > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
>  > >  > the system shared re0 interrupt with OHCI and this caused
>  > >  > re(4) to corrupt packets and create interrupt storms. Tried
>  > > 
>  > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
>  > > triggered on systems with > 4GB memory. But I dont' know whether
>  > > this is related with interrupt storms.
>  > > 
>  > >  > updating to 7.1 -BETA2 and still had some problems with it.
>  > >  > 
>  > >  > I've opened the PR kern/128287[2] and Remko quickly answered
>  > >  > with a workaround: that workaround was removing USB support from
>  > >  > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
>  > >  > and the interrupt storms were gone. Now sometime later the interface
>  > >  > goes up and down from time to time, but less often. Also sometimes
>  > >  > the machine losts the network interface but continues to work.
>  > >  > 
>  > > 
>  > > It seems that your controller supports MSI so you can set a tunable
>  > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
>  > > interrupt sharing(e.g. add hw.re.msi_disable="0" to
>  > > /boot/loader.conf file.) However there were several issues on re(4)
>  > > w.r.t MSI so it was off by default.
>  > 
>  > This is undocumented and with sysctl -a i can't find the tunable. Is this
>  > a HEAD feature or it's also in 7.1 -BETA2? Should i add
> 
> Yeah it's an undocmented feature. But most drivers written by me
> have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have
> the tunable.

I think it could be great if you could document it or at least
show it by default when you do sysctl -ad with a small description.

> 
>  > hw.re_msi_disable="0" to /boot/loader.conf?
>    ^^^^^^^^^^^^^^^^^^^^^
>    Shoule be hw.re.msi_disable="0"
>  > 
> 
> Yes, just add it to /boot/loader.conf. Note, you should not disable
> system-wide MSI control(e.g. hw.pci.enable_msi == 1).
> 
>  > This was sharing interrupt with USB, does USB need any special MSI handling
>  > or with re using MSI is enough to not share the interrupt?
> 
> If re(4) can use MSI, you don't need to worry about interrupt
> sharing with USB. Check the output of "vmstat -i". You normally get
> an irq256 or higher for MSI enabled driver.
> 
>  > 
>  > 
>  > > 
>  > >  > I know it continues to work because some days later i can see that
>  > >  > it tried to deliver the status reports but was unable to resolve the
>  > >  > aliases hostnames. I can't ping the machine and i know the network
>  > >  > is OK. If i reboot the machine everything is working again.
>  > >  > 
>  > > 
>  > > Recently I've made small changes to re(4) which may help to detect
>  > > link state change event. Would you try re(4) in HEAD?
>  > 
>  > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that
> 
> Yes, you can. It should build without problems. Just replace re(4) on
> stable/7 with HEAD version.
> 
>  > or do i need to test the whole HEAD kernel?
>  > 
> 
> No you don't have to that.

Backporting the changes i've found that it didn't compile so in
the end i got from HEAD the following files:

base/head/sys/dev/re/if_re.c
base/head/sys/pci/if_rl.c
base/head/sys/pci/if_rlreg.h

After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled
the knob you suggested in /boot/loader.conf.

With the new kernel and MSI the interrupts are like this:

# vmstat -i
interrupt                          total       rate
irq9: acpi0                            1          0
irq16: ohci0                           1          0
irq17: ohci1 ohci3                     1          0
irq18: ohci2 ohci4                     1          0
irq22: atapci0                     19215         15
cpu0: timer                      2502718       1998
irq256: re0                      4967726       3967
cpu1: timer                      2502525       1998
Total                            9992188       7980

The high interrupt numbers are because i've been running iperf to
check everything it's fine, not because of interrupt storms. So far
i didn't find any interrupt storms related to USB or re(4) driver
but while doing the tests i've found this error:

re0: watchdog timeout (missed Tx interrupts) -- recovering

This didn't create any error on the interfaces (netstat -i).

Also i didn't see any problem with interfaces going up and down,
but that usually happen after some hours of uptime, so i'll let
you know if the error happens again.

As these seems to improve the current situation, is there any
chance of merging -current driver in 7.1 before release?

Thanks!
Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From arnaud.houdelette at tzim.net  Wed Dec 10 04:18:06 2008
From: arnaud.houdelette at tzim.net (Arnaud Houdelette)
Date: Wed Dec 10 06:10:52 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081209185236.GA1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
Message-ID: <493FB378.5030106@tzim.net>

Victor Balada Diaz a ?crit :
> Hello,
>
> I got various machines[1] at hetzner.de and I've been having problems
> with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
> been trying to narrow the problem so someone more knowledgeable than me
> is able to fix it. This mail is an other attempt to ask a question
> with regards ATA code to see if this time i got something.
>
> For the ones that don't actually know what happened:
>
> With FreeBSD 7.0 -RELEASE for amd64 and default kernel
> the system shared re0 interrupt with OHCI and this caused
> re(4) to corrupt packets and create interrupt storms. Tried
> updating to 7.1 -BETA2 and still had some problems with it.
>
> I've opened the PR kern/128287[2] and Remko quickly answered
> with a workaround: that workaround was removing USB support from
> my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
> and the interrupt storms were gone. Now sometime later the interface
> goes up and down from time to time, but less often. Also sometimes
> the machine losts the network interface but continues to work.
>
> I know it continues to work because some days later i can see that
> it tried to deliver the status reports but was unable to resolve the
> aliases hostnames. I can't ping the machine and i know the network
> is OK. If i reboot the machine everything is working again.
>
> When switched from 7.0 to 7.1 BETA2 i also found that under load
> after some hours the machine created interrupt storms on ATA disks.
>
> Digging at linux source code i've found that they do some special things
> for this chipset that i've been unable to find on our code. This is
> linux code for my chipset:
>
> 371                 AHCI_HFLAGS     (AHCI_HFLAG_IGN_SERR_INTERNAL |
> 372                                  AHCI_HFLAG_32BIT_ONLY | AHCI_HFLAG_NO_MSI |
> 373                                  AHCI_HFLAG_SECT255),
>
> File and the rest of the code in here[3].
>
> As i saw AHCI_HFLAG_NO_MSI i tried doing the easiest thing i could
> think of, switching MSI and MSI-x off for the whole system, so
> i added to /boot/loader.conf this tunables:
>
> hw.pci.enable_msix="0"
> hw.pci.enable_msi="0"
>
> And then rebooted the machine. After various hours of doing almost nothing
> i've found that the machine answered ping but was unable to answer any
> request (eg, ssh, nagios nrpe, etc). The machine recovered itself after
> some minutes and when i was able to ssh into i saw the following in dmesg:
>
> ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
> ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
> ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
> ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
> ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
> ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1463123158
>
> and a lot more errors like that. I didn't get this errors with MSI enabled.
> I see WRITE_DMA48 and in linux code i saw AHCI_HFLAG_32BIT_ONLY which is later
> used for DMA related things. Could someone who is more knowledgeable check
> if we're doing the right thing?
>
> I've attached verbose dmesg of a machine that's like this one with
> 7.1 -BETA2, MSI enabled and GENERIC kernel minus USB and firewrire.
>
> Also, please, could someone give me a hand on how could i continue debugging
> this interrupt issues? I'm a bit lost and digging code and posting each
> time i think i've found something is not going to go anywhere.
>
> I would also like to say that i've seen reports of this kind of problems
> on amd64 machines in the lists since various years ago, so i don't think
> this is just a problem with this BIOS/motherboard (MSI K9AG Neo2 Digital)
> on the lists
>
>
> Thanks in advance for any help.
> Regards.
>
>
> [1]: http://www.hetzner.de/hosting/produkte_rootserver/ds7000/
> [2]: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287
> [3]: http://fxr.watson.org/fxr/source/drivers/ata/ahci.c?v=linux-2.6#L369
>   

Sorry I didn't take the time to read all the thread, but I got similar 
problem with the same IXP600 chipset.
Only it was'nt with a Realtek NIC (re) but with a Ralink wireless one. 
The simptoms where similar : interrupt 22 was shared between the sata 
controler and the wireless card. And I got Interrupt Storms at random 
times when using the wireless network.

No problem since I removed the ral(4) NIC (got a real access point now).
You might not want to point the finger at the re(4) driver too fast.

Arnaud Houdelette


From lists at peter.de.com  Wed Dec 10 04:25:43 2008
From: lists at peter.de.com (Oliver Peter)
Date: Wed Dec 10 06:11:45 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081209185236.GA1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
Message-ID: <20081210120840.GA36443@nemesis.frida.mouhaha.de>

On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
> Hello,
> 
> I got various machines[1] at hetzner.de and I've been having problems
> with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
> been trying to narrow the problem so someone more knowledgeable than me
> is able to fix it. This mail is an other attempt to ask a question
> with regards ATA code to see if this time i got something.

Just want to add a quick note and say that I'm having the same problem
with my 7.0-RELEASE-p6/amd64 hetzner machine:

     http://lists.freebsd.org/pipermail/freebsd-acpi/2008-September/005095.html

I would be happy to test patches as well.  Thanks.

-- 
Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174
"If it feels good, you're doing something wrong."
                                      -- Coach McTavish
From rabing at omc.net  Wed Dec 10 05:18:18 2008
From: rabing at omc.net (Lutz Rabing)
Date: Wed Dec 10 06:11:59 2008
Subject: AMD Phenom(tm) 8450 Triple-Core Processor does not boot
	7.1-PRERELESE
Message-ID: <493FBDEC.7010301@omc.net>

hi,

I just upgraded a new system with an AMD "Triple-Core" CPU from amd64 7.0-RELEASE to
amd64 7.1-PRERELEASE. the boot process hangs after "SMP: AP CPU #2 Launched!"

as you can see from the attached dmesg output 7.0-RELEASE does boot. is this a known
problem, or is there anything I can do?

best regards,
lutz rabing

#-------------------------

Dec 10 01:20:49 xXx kernel: FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008
Dec 10 21:22:24 xXx kernel: root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Dec 10 21:22:24 xXx kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Dec 10 21:22:24 xXx kernel: CPU: AMD Phenom(tm) 8450 Triple-Core Processor (2109.33-MHz K8-class CPU)
Dec 10 21:22:24 xXx kernel: Origin = "AuthenticAMD"  Id = 0x100f23  Stepping = 3
Dec 10 21:22:24 xXx kernel:
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Dec 10 21:22:24 xXx kernel: Features2=0x802009<SSE3,MON,CX16,<b23>>
Dec 10 21:22:24 xXx kernel: AMD Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,<b26>,RDTSCP,LM,3DNow!+,3DNow!>
Dec 10 21:22:24 xXx kernel: AMD Features2=0x7ff<LAHF,CMP,SVM,ExtAPIC,CR8,<b5>,<b6>,<b7>,Prefetch,<b9>,<b10>>
Dec 10 21:22:24 xXx kernel: Cores per package: 3
Dec 10 21:22:24 xXx kernel: usable memory = 8308195328 (7923 MB)
Dec 10 21:22:24 xXx kernel: avail memory  = 8028749824 (7656 MB)
Dec 10 21:22:24 xXx kernel: ACPI APIC Table: <091908 APIC1057>
Dec 10 21:22:24 xXx kernel: FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs
Dec 10 21:22:24 xXx kernel: cpu0 (BSP): APIC ID:  0
Dec 10 21:22:24 xXx kernel: cpu1 (AP): APIC ID:  1
Dec 10 21:22:24 xXx kernel: cpu2 (AP): APIC ID:  2
Dec 10 21:22:24 xXx kernel: ioapic0 <Version 2.1> irqs 0-23 on motherboard
Dec 10 21:22:24 xXx kernel: kbd1 at kbdmux0
Dec 10 21:22:24 xXx kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Dec 10 21:22:24 xXx kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18)
Dec 10 21:22:24 xXx kernel: acpi0: <091908 RSDT1057> on motherboard
Dec 10 21:22:24 xXx kernel: acpi0: [ITHREAD]
Dec 10 21:22:24 xXx kernel: acpi0: Power Button (fixed)
Dec 10 21:22:24 xXx kernel: acpi0: reservation of ffb80000, 80000 (3) failed
Dec 10 21:22:24 xXx kernel: acpi0: reservation of 0, a0000 (3) failed
Dec 10 21:22:24 xXx kernel: acpi0: reservation of 100000, cff00000 (3) failed
Dec 10 21:22:24 xXx kernel: ACPI HPET table warning: Sequence is non-zero (2)
Dec 10 21:22:24 xXx kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Dec 10 21:22:24 xXx kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
Dec 10 21:22:24 xXx kernel: acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Dec 10 21:22:24 xXx kernel: acpi_hpet0: HPET never increments, disabling
Dec 10 21:22:24 xXx kernel: device_attach: acpi_hpet0 attach returned 6
Dec 10 21:22:24 xXx kernel: cpu0: <ACPI CPU> on acpi0
Dec 10 21:22:24 xXx kernel: acpi_throttle0: <ACPI CPU Throttling> on cpu0
Dec 10 21:22:24 xXx kernel: cpu1: <ACPI CPU> on acpi0
Dec 10 21:22:24 xXx kernel: cpu2: <ACPI CPU> on acpi0
...
Dec 10 21:22:24 xXx kernel: SMP: AP CPU #2 Launched!
Dec 10 21:22:24 xXx kernel: SMP: AP CPU #1 Launched!
...


From victor at bsdes.net  Wed Dec 10 06:01:32 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:12:10 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210120840.GA36443@nemesis.frida.mouhaha.de>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210120840.GA36443@nemesis.frida.mouhaha.de>
Message-ID: <20081210140129.GE1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 12:08:40PM +0000, Oliver Peter wrote:
> On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
> > Hello,
> > 
> > I got various machines[1] at hetzner.de and I've been having problems
> > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
> > been trying to narrow the problem so someone more knowledgeable than me
> > is able to fix it. This mail is an other attempt to ask a question
> > with regards ATA code to see if this time i got something.
> 
> Just want to add a quick note and say that I'm having the same problem
> with my 7.0-RELEASE-p6/amd64 hetzner machine:
> 
>      http://lists.freebsd.org/pipermail/freebsd-acpi/2008-September/005095.html
> 
> I would be happy to test patches as well.  Thanks.

Hello Oliver,

What i did so far and improved a lot the experience was:

1) Upgrade at least the if_re code to RELENG_7. This fixes issues
   of packet corruption on ssh sessions.

2) Delete from your kernel config USB and firewire. This prevents
   the realtek interrupt to be shared.

After this, with 7.1 -BETA2 the systems are more or less stable, but
after a while the ATA controller starts to create interrupt storms.
I wasn't able to find why.

With the help that i've received in this thread from Pyun
YongHyeon (Thanks!!) i'm also trying this suggestions:

3) Backport this 3 files from current to 7.1 -BETA2:

base/head/sys/dev/re/if_re.c
base/head/sys/pci/if_rl.c
base/head/sys/pci/if_rlreg.h

You can fetch them from http://svn.freebsd.org/. With them and
adding to /boot/loader.conf this tunable:

hw.re.msi_disable="0"

I can use GENERIC kernel again (ie, USB enabled) and so far
i didn't find any problem yet. No more interface up/down problems
and no more interrupt storms. I must say that i haven't tested
this enough, because the interrupt storms in ATA code start to
happen after a few days of uptime load, but at least the problems
with the realtek seem to be gone. 

If you upgrade to 7.1 -BETA2 you'll also get SATA support for
the IXP card. With 7.0 it will work as ATA 33 in compatibility mode.

Maybe someone with write access to the wiki could add it somewhere
so that other hetzner users that are having the same problems
could use the same workarounds :)

I hope this helps you.

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From victor at bsdes.net  Wed Dec 10 06:08:26 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:12:29 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
Message-ID: <20081210140823.GF1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
> On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
>  > On Wed, Dec 10, 2008 at 07:28:00PM +0900, Pyun YongHyeon wrote:
>  > > On Wed, Dec 10, 2008 at 09:59:35AM +0100, Victor Balada Diaz wrote:
>  > >  > On Wed, Dec 10, 2008 at 03:12:26PM +0900, Pyun YongHyeon wrote:
>  > >  > > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
>  > >  > >  > Hello,
>  > >  > >  > 
>  > >  > >  > I got various machines[1] at hetzner.de and I've been having problems
>  > >  > >  > with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
>  > >  > >  > been trying to narrow the problem so someone more knowledgeable than me
>  > >  > >  > is able to fix it. This mail is an other attempt to ask a question
>  > >  > >  > with regards ATA code to see if this time i got something.
>  > >  > >  > 
>  > >  > >  > For the ones that don't actually know what happened:
>  > >  > >  > 
>  > >  > >  > With FreeBSD 7.0 -RELEASE for amd64 and default kernel
>  > >  > >  > the system shared re0 interrupt with OHCI and this caused
>  > >  > >  > re(4) to corrupt packets and create interrupt storms. Tried
>  > >  > > 
>  > >  > > re(4) in 7.0-RELEASE had bus_dma(9) bug which could be easily
>  > >  > > triggered on systems with > 4GB memory. But I dont' know whether
>  > >  > > this is related with interrupt storms.
>  > >  > > 
>  > >  > >  > updating to 7.1 -BETA2 and still had some problems with it.
>  > >  > >  > 
>  > >  > >  > I've opened the PR kern/128287[2] and Remko quickly answered
>  > >  > >  > with a workaround: that workaround was removing USB support from
>  > >  > >  > my kernel. I did it and re(4) wasn't sharing interrupts anylonger,
>  > >  > >  > and the interrupt storms were gone. Now sometime later the interface
>  > >  > >  > goes up and down from time to time, but less often. Also sometimes
>  > >  > >  > the machine losts the network interface but continues to work.
>  > >  > >  > 
>  > >  > > 
>  > >  > > It seems that your controller supports MSI so you can set a tunable
>  > >  > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
>  > >  > > interrupt sharing(e.g. add hw.re.msi_disable="0" to
>  > >  > > /boot/loader.conf file.) However there were several issues on re(4)
>  > >  > > w.r.t MSI so it was off by default.
>  > >  > 
>  > >  > This is undocumented and with sysctl -a i can't find the tunable. Is this
>  > >  > a HEAD feature or it's also in 7.1 -BETA2? Should i add
>  > > 
>  > > Yeah it's an undocmented feature. But most drivers written by me
>  > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have
>  > > the tunable.
>  > 
>  > I think it could be great if you could document it or at least
>  > show it by default when you do sysctl -ad with a small description.
>  > 
> 
> If MSI worked as expected I would have documented it as I did
> in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc.
> Using MSI on RealTek does not seem to stable. I tried hard to fix
> that but some users still reported watchdog timeouts. Working
> without documentation and hardware also made it hard to complete
> the work. This was the main reason why MSI was disabled on re(4).

What do you think about adding a note in the man page telling that
it's experimental and in some cases it could improve the situation
but in others it will give errors? 

> 
>  > > 
>  > >  > hw.re_msi_disable="0" to /boot/loader.conf?
>  > >    ^^^^^^^^^^^^^^^^^^^^^
>  > >    Shoule be hw.re.msi_disable="0"
>  > >  > 
>  > > 
>  > > Yes, just add it to /boot/loader.conf. Note, you should not disable
>  > > system-wide MSI control(e.g. hw.pci.enable_msi == 1).
>  > > 
>  > >  > This was sharing interrupt with USB, does USB need any special MSI handling
>  > >  > or with re using MSI is enough to not share the interrupt?
>  > > 
>  > > If re(4) can use MSI, you don't need to worry about interrupt
>  > > sharing with USB. Check the output of "vmstat -i". You normally get
>  > > an irq256 or higher for MSI enabled driver.
>  > > 
>  > >  > 
>  > >  > 
>  > >  > > 
>  > >  > >  > I know it continues to work because some days later i can see that
>  > >  > >  > it tried to deliver the status reports but was unable to resolve the
>  > >  > >  > aliases hostnames. I can't ping the machine and i know the network
>  > >  > >  > is OK. If i reboot the machine everything is working again.
>  > >  > >  > 
>  > >  > > 
>  > >  > > Recently I've made small changes to re(4) which may help to detect
>  > >  > > link state change event. Would you try re(4) in HEAD?
>  > >  > 
>  > >  > Can i just drop HEAD's /stable/7/sys/dev/re/ in -STABLE and test that
>  > > 
>  > > Yes, you can. It should build without problems. Just replace re(4) on
>  > > stable/7 with HEAD version.
>  > > 
>  > >  > or do i need to test the whole HEAD kernel?
>  > >  > 
>  > > 
>  > > No you don't have to that.
>  > 
>  > Backporting the changes i've found that it didn't compile so in
>  > the end i got from HEAD the following files:
>  > 
>  > base/head/sys/dev/re/if_re.c
>  > base/head/sys/pci/if_rl.c
>  > base/head/sys/pci/if_rlreg.h
>  > 
> 
> Ah,, sorry about that. Recently there was some changes. I forgot
> that.
> 
>  > After that i've recompiled 7.1 -BETA2 GENERIC kernel and enabled
>  > the knob you suggested in /boot/loader.conf.
>  > 
>  > With the new kernel and MSI the interrupts are like this:
>  > 
>  > # vmstat -i
>  > interrupt                          total       rate
>  > irq9: acpi0                            1          0
>  > irq16: ohci0                           1          0
>  > irq17: ohci1 ohci3                     1          0
>  > irq18: ohci2 ohci4                     1          0
>  > irq22: atapci0                     19215         15
>  > cpu0: timer                      2502718       1998
>  > irq256: re0                      4967726       3967
>  > cpu1: timer                      2502525       1998
>  > Total                            9992188       7980
>  > 
>  > The high interrupt numbers are because i've been running iperf to
>  > check everything it's fine, not because of interrupt storms. So far
>  > i didn't find any interrupt storms related to USB or re(4) driver
>  > but while doing the tests i've found this error:
>  > 
>  > re0: watchdog timeout (missed Tx interrupts) -- recovering
>  > 
>  > This didn't create any error on the interfaces (netstat -i).
>  > 
> 
> This was triggered by new code in HEAD. It indicates re(4) missed
> Tx completion interrupt. It could be a bug in driver or hardware
> bug. If you can live with that message you can safely ignore that
> as now re(4) does not reinitialize the hardware if it detect
> missing Tx completion interrupt.

Yeah, just happened once, and i'm used to receiving a lot of interface
UP/DOWN messages that now are gone, so this is an improvement.

> 
>  > Also i didn't see any problem with interfaces going up and down,
>  > but that usually happen after some hours of uptime, so i'll let
>  > you know if the error happens again.
>  > 
> 
> Ok.
> 
>  > As these seems to improve the current situation, is there any
>  > chance of merging -current driver in 7.1 before release?
>  > 
> 
> I think re(4) in HEAD needs more testing. As you might know RealTek
> produced too many chipsets. :-(

Ok, i'll use the backported driver as it works better for me :-)

If i can help you testing any patches i'm more than welcome to do it.

Thanks a lot for your help Pyun YongHyeon.

Regards.
-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From lists at peter.de.com  Wed Dec 10 06:18:47 2008
From: lists at peter.de.com (Oliver Peter)
Date: Wed Dec 10 06:29:21 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210140129.GE1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210120840.GA36443@nemesis.frida.mouhaha.de>
	<20081210140129.GE1320@alf.bsdes.net>
Message-ID: <20081210141834.GB36443@nemesis.frida.mouhaha.de>

On Wed, Dec 10, 2008 at 03:01:30PM +0100, Victor Balada Diaz wrote:
> On Wed, Dec 10, 2008 at 12:08:40PM +0000, Oliver Peter wrote:
> > On Tue, Dec 09, 2008 at 07:52:37PM +0100, Victor Balada Diaz wrote:
...
> I can use GENERIC kernel again (ie, USB enabled) and so far
> i didn't find any problem yet. No more interface up/down problems
> and no more interrupt storms. I must say that i haven't tested
> this enough, because the interrupt storms in ATA code start to
> happen after a few days of uptime load, but at least the problems
> with the realtek seem to be gone. 

I found out that I'm able to 'force' the interrupt storm by provoking
higher disk I/O.  Just let dd write to a file in a loop for some hours
and watch vmstat:

    while true; do dd if=/dev/zero of=BLA bs=1M count=1000; done

First you'll see that the throughput will decrease, and a few
hours later you'll have /var/log/messages / dmesg full of
interrupt storm messages.
 
> If you upgrade to 7.1 -BETA2 you'll also get SATA support for
> the IXP card. With 7.0 it will work as ATA 33 in compatibility mode.

Wow!  That's good to hear as well.  I'll definitely switch to
-STABLE or 7.1-PRERELASE sooner or later.  I'll just give it a try
on my other machines at first.
 
> I hope this helps you.

Absolutely, cheers mate.  I owe you one!

~ollie

-- 
Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174
"If it feels good, you're doing something wrong."
                                      -- Coach McTavish
From victor at bsdes.net  Wed Dec 10 06:21:08 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Wed Dec 10 06:29:31 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <493FB378.5030106@tzim.net>
References: <20081209185236.GA1320@alf.bsdes.net> <493FB378.5030106@tzim.net>
Message-ID: <20081210142107.GG1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 01:18:00PM +0100, Arnaud Houdelette wrote:
> Victor Balada Diaz a ?crit :
> >Hello,
> >
> >I got various machines[1] at hetzner.de and I've been having problems
> >with interrupts on FreeBSD 7.0 and now FreeBSD 7.1 -BETA2 in amd64. I've
> >been trying to narrow the problem so someone more knowledgeable than me
> >is able to fix it. This mail is an other attempt to ask a question
> >with regards ATA code to see if this time i got something.
> >
> >[...] 
> 
> Sorry I didn't take the time to read all the thread, but I got similar 
> problem with the same IXP600 chipset.
> Only it was'nt with a Realtek NIC (re) but with a Ralink wireless one. 
> The simptoms where similar : interrupt 22 was shared between the sata 
> controler and the wireless card. And I got Interrupt Storms at random 
> times when using the wireless network.
> 
> No problem since I removed the ral(4) NIC (got a real access point now).
> You might not want to point the finger at the re(4) driver too fast.
> 
> Arnaud Houdelette
Hello Arnaud,

I didn't say the problem was just because of re(4). Actually i think the
there were two problems, one with re(4) and other with ata(4). The reason
why i talked about both of them in the same mail is because i thought
that as two drivers were affected, maybe the problem was in other part
of the operating system and that could help the developers to debug the
problem.

My re(4) card isn't sharing the interrupt with IXP600, it's sharing
the interrupt with USB controller. In this case i think the problem
is fixed with the advices from Pyun YongHyeon (backporting the driver
from HEAD and using MSI for interrupts).

I think the problems with ata(4) code will appear again after a few
days of load, as they always do, so i'll keep trying to debug them.

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From peterjeremy at optushome.com.au  Wed Dec 10 10:06:03 2008
From: peterjeremy at optushome.com.au (Peter Jeremy)
Date: Wed Dec 10 10:06:10 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>
References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru>
	<20081210091107.GC1320@alf.bsdes.net>
	<A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>
Message-ID: <20081210180559.GC58682@server.vk2pj.dyndns.org>

On 2008-Dec-10 10:55:35 +0100, S?ren Schmidt <sos@freebsd.org> wrote:
>And you will not use 64bit DMA even if the chipset supports it.  
>However I have not seen any chipsets supporting this fail, YMMV as  
>usual :)

There's a reference in wikipedia pointing to
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06694.html
that claims the AMD/ATI SB600 lies about supporting 64-bit DMA in AHCI
mode.  I have a SB600 but it doesn't have >4GB to test on.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081210/08e2de87/attachment.pgp
From gallasch at free.de  Wed Dec 10 17:10:04 2008
From: gallasch at free.de (Kai Gallasch)
Date: Wed Dec 10 17:16:27 2008
Subject: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64]
Message-ID: <200812110108.mBB18EaG012561@www.freebsd.org>


>Number:         129563
>Category:       amd64
>Synopsis:       [ACPI] sleep broken on IBM/Lenovo T61 [amd64]
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 11 01:10:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Kai Gallasch
>Release:        amd64 7.1 PRERELEASE 20081211
>Organization:
>Environment:
FreeBSD boskoop.free.de 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #5: Thu Dec 11 01:09:49 CET 2008     root@boskoop.free.de:/usr/obj/usr/src/sys/IBM-T61  amd64
>Description:
Trying to put IBM/Lenovo Notebook T61 into supported sleep modes through command "acpiconf" provokes an error:

~ # acpiconf -s5
acpiconf: invalid sleep type (5)

~ # acpiconf -s4
acpiconf: request sleep type (4) failed: Operation not supported

~ # acpiconf -s3
acpiconf: request sleep type (3) failed: Operation not supported


~ # sysctl -a | grep sleep_state
hw.acpi.supported_sleep_state: S3 S4 S5


---- dmesg ----

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-PRERELEASE #5: Thu Dec 11 01:09:49 CET 2008
    root@boskoop.free.de:/usr/obj/usr/src/sys/IBM-T61
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz (2493.77-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x8e3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b19>>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 2
usable memory = 2119114752 (2020 MB)
avail memory  = 2044940288 (1950 MB)
ACPI APIC Table: <LENOVO TP-7L   >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length:        0    102C/0 [20070320]
ioapic0: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <LENOVO TP-7L> on motherboard
acpi0: [ITHREAD]
acpi_ec0: <Embedded Controller: GPE 0x12, ECDT> port 0x62,0x66 on acpi0
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7ef00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x2000-0x207f mem 0xd2000000-0xd2ffffff,0xe0000000-0xefffffff,0xd0000000-0xd1ffffff irq 16 at device 0.0 on pci1
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x1840-0x185f mem 0xfe200000-0xfe21ffff,0xfe225000-0xfe225fff irq 20 at device 25.0 on pci0
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:1c:25:74:d1:01
uhci0: <Intel 82801H (ICH8) USB controller USB-D> port 0x1860-0x187f irq 20 at device 26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <Intel 82801H (ICH8) USB controller USB-D> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801H (ICH8) USB controller USB-E> port 0x1880-0x189f irq 21 at device 26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <Intel 82801H (ICH8) USB controller USB-E> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <Intel 82801H (ICH8) USB 2.0 controller USB2-B> mem 0xfe226c00-0xfe226fff irq 22 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <Intel 82801H (ICH8) USB 2.0 controller USB2-B> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 4 ports with 4 removable, self powered
pcm0: <Intel 82801H High Definition Audio Controller> mem 0xfe220000-0xfe223fff irq 17 at device 27.0 on pci0
pcm0: [ITHREAD]
pcib2: <ACPI PCI-PCI bridge> irq 20 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pci2: <memory> at device 0.0 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> irq 21 at device 28.1 on pci0
pci3: <ACPI PCI bus> on pcib3
pci3: <network> at device 0.0 (no driver attached)
pcib4: <ACPI PCI-PCI bridge> irq 22 at device 28.2 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 23 at device 28.3 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 20 at device 28.4 on pci0
pci13: <ACPI PCI bus> on pcib6
uhci2: <Intel 82801H (ICH8) USB controller USB-A> port 0x18a0-0x18bf irq 16 at device 29.0 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb3: <Intel 82801H (ICH8) USB controller USB-A> on uhci2
usb3: USB revision 1.0
uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
uhci3: <Intel 82801H (ICH8) USB controller USB-B> port 0x18c0-0x18df irq 17 at device 29.1 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <Intel 82801H (ICH8) USB controller USB-B> on uhci3
usb4: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
uhci4: <Intel 82801H (ICH8) USB controller USB-C> port 0x18e0-0x18ff irq 18 at device 29.2 on pci0
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <Intel 82801H (ICH8) USB controller USB-C> on uhci4
usb5: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
uhub5: 2 ports with 2 removable, self powered
ehci1: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> mem 0xfe227000-0xfe2273ff irq 19 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <Intel 82801H (ICH8) USB 2.0 controller USB2-A> on ehci1
usb6: USB revision 2.0
uhub6: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb6
uhub6: 6 ports with 6 removable, self powered
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci21: <ACPI PCI bus> on pcib7
cbb0: <RF5C476 PCI-CardBus Bridge> mem 0xf8100000-0xf8100fff irq 16 at device 0.0 on pci21
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH8M UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1830-0x183f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
atapci1: <Intel AHCI controller> port 0x1c48-0x1c4f,0x1c1c-0x1c1f,0x1c40-0x1c47,0x1c18-0x1c1b,0x1c20-0x1c3f mem 0xfe226000-0xfe2267ff irq 16 at device 31.2 on pci0
atapci1: [ITHREAD]
atapci1: AHCI Version 01.10 controller with 3 ports detected
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: port not implemented
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci1
ata4: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Synaptics Touchpad, device ID 0
battery0: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_ibm0: <IBM ThinkPad ACPI Extras> on acpi0
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcefff,0xcf000-0xcffff,0xd0000-0xd0fff,0xd1000-0xd3fff,0xe0000-0xeffff on isa0
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ubt0: <Broadcom Corp BCM2045B, class 224/1, rev 2.00/1.00, addr 2> on uhub0
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320
ugen0: <STMicroelectronics Biometric Coprocessor, class 0/0, rev 1.00/0.01, addr 3> on uhub0
Timecounters tick every 1.000 msec
acd0: DVDR <Optiarc DVD RW AD-7910A/1.D1> at ata0-master UDMA33
ad4: 152627MB <FUJITSU MHW2160BJ G1 0084001D> at ata2-master SATA150
pcm0: <HDA Codec: Analog Devices AD1984>
pcm0: <HDA Driver Revision: 20080420_0052>
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s2a
WARNING: attempt to net_add_domain(bluetooth) after domainfinalize()
WARNING: attempt to net_add_domain(netgraph) after domainfinalize()

---- dmesg: END ----

---- kldstat ----

boskoop:~ # kldstat 
Id Refs Address            Size     Name
 1   13 0xffffffff80100000 7acee8   kernel
 2    1 0xffffffff808ad000 1a6e8    snd_hda.ko
 3    2 0xffffffff808c8000 66408    sound.ko
 4    1 0xffffffff8092f000 5300     acpi_ibm.ko
 5    1 0xffffffff80935000 9590     ng_ubt.ko
 6    6 0xffffffff8093f000 14398    netgraph.ko
 7    4 0xffffffffaeea6000 81e      ng_bluetooth.ko
 8    1 0xffffffffaeea7000 8742     ng_hci.ko
 9    1 0xffffffffaeeb0000 ad40     ng_l2cap.ko
10    1 0xffffffffaeebb000 126e2    ng_btsocket.ko
11    1 0xffffffffaeece000 183e     ng_socket.ko

---- kldstat: END ----

---- sysctl -a | grep acpi ----

~ # sysctl -a | grep acpi
debug.acpi.semaphore_debug: 0
debug.acpi.suspend_bounce: 0
debug.acpi.do_powerstate: 1
debug.acpi.acpi_ca_version: 20070320
debug.acpi.ec.timeout: 750
debug.acpi.ec.polled: 0
debug.acpi.ec.burst: 0
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.thermal.min_runtime: 0
hw.acpi.thermal.polling_rate: 10
hw.acpi.thermal.user_override: 0
hw.acpi.thermal.tz0.temperature: 42.0C
hw.acpi.thermal.tz0.active: -1
hw.acpi.thermal.tz0.passive_cooling: 0
hw.acpi.thermal.tz0.thermal_flags: 0
hw.acpi.thermal.tz0._PSV: -1
hw.acpi.thermal.tz0._HOT: -1
hw.acpi.thermal.tz0._CRT: 127.0C
hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
hw.acpi.thermal.tz0._TC1: -1
hw.acpi.thermal.tz0._TC2: -1
hw.acpi.thermal.tz0._TSP: -1
hw.acpi.thermal.tz1.temperature: 36.0C
hw.acpi.thermal.tz1.active: -1
hw.acpi.thermal.tz1.passive_cooling: 1
hw.acpi.thermal.tz1.thermal_flags: 0
hw.acpi.thermal.tz1._PSV: 95.5C
hw.acpi.thermal.tz1._HOT: -1
hw.acpi.thermal.tz1._CRT: 100.0C
hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
hw.acpi.thermal.tz1._TC1: 5
hw.acpi.thermal.tz1._TC2: 4
hw.acpi.thermal.tz1._TSP: 600
hw.acpi.battery.life: 99
hw.acpi.battery.time: -1
hw.acpi.battery.state: 0
hw.acpi.battery.units: 1
hw.acpi.battery.info_expire: 5
hw.acpi.acline: 1
hw.acpi.cpu.cx_lowest: C1
machdep.acpi_timer_freq: 3579545
machdep.acpi_root: 1009872
dev.acpi.0.%desc: LENOVO TP-7L
dev.acpi.0.%driver: acpi
dev.acpi.0.%parent: nexus0
dev.acpi_ec.0.%desc: Embedded Controller: GPE 0x12, ECDT
dev.acpi_ec.0.%driver: acpi_ec
dev.acpi_ec.0.%location: handle=\_SB_.PCI0.LPC_.EC__
dev.acpi_ec.0.%pnpinfo: _HID=PNP0C09 _UID=0
dev.acpi_ec.0.%parent: acpi0
dev.acpi_sysresource.0.%desc: System Resource
dev.acpi_sysresource.0.%driver: acpi_sysresource
dev.acpi_sysresource.0.%location: handle=\_SB_.MEM_
dev.acpi_sysresource.0.%pnpinfo: _HID=PNP0C01 _UID=0
dev.acpi_sysresource.0.%parent: acpi0
dev.acpi_sysresource.1.%desc: System Resource
dev.acpi_sysresource.1.%driver: acpi_sysresource
dev.acpi_sysresource.1.%location: handle=\_SB_.PCI0.LPC_.SIO_
dev.acpi_sysresource.1.%pnpinfo: _HID=PNP0C02 _UID=0
dev.acpi_sysresource.1.%parent: acpi0
dev.acpi_timer.0.%desc: 24-bit timer at 3.579545MHz
dev.acpi_timer.0.%driver: acpi_timer
dev.acpi_timer.0.%location: unknown
dev.acpi_timer.0.%pnpinfo: unknown
dev.acpi_timer.0.%parent: acpi0
dev.pci_link.0.%parent: acpi0
dev.pci_link.1.%parent: acpi0
dev.pci_link.2.%parent: acpi0
dev.pci_link.3.%parent: acpi0
dev.pci_link.4.%parent: acpi0
dev.pci_link.5.%parent: acpi0
dev.pci_link.6.%parent: acpi0
dev.pci_link.7.%parent: acpi0
dev.acpi_hpet.0.%desc: High Precision Event Timer
dev.acpi_hpet.0.%driver: acpi_hpet
dev.acpi_hpet.0.%location: unknown
dev.acpi_hpet.0.%pnpinfo: unknown
dev.acpi_hpet.0.%parent: acpi0
dev.acpi_lid.0.%desc: Control Method Lid Switch
dev.acpi_lid.0.%driver: acpi_lid
dev.acpi_lid.0.%location: handle=\_SB_.LID_
dev.acpi_lid.0.%pnpinfo: _HID=PNP0C0D _UID=0
dev.acpi_lid.0.%parent: acpi0
dev.acpi_lid.0.wake: 1
dev.acpi_button.0.%desc: Sleep Button
dev.acpi_button.0.%driver: acpi_button
dev.acpi_button.0.%location: handle=\_SB_.SLPB
dev.acpi_button.0.%pnpinfo: _HID=PNP0C0E _UID=0
dev.acpi_button.0.%parent: acpi0
dev.acpi_button.0.wake: 1
dev.pcib.0.%parent: acpi0
dev.acpi_tz.0.%desc: Thermal Zone
dev.acpi_tz.0.%driver: acpi_tz
dev.acpi_tz.0.%location: handle=\_TZ_.THM0
dev.acpi_tz.0.%pnpinfo: _HID=none _UID=0
dev.acpi_tz.0.%parent: acpi0
dev.acpi_tz.1.%desc: Thermal Zone
dev.acpi_tz.1.%driver: acpi_tz
dev.acpi_tz.1.%location: handle=\_TZ_.THM1
dev.acpi_tz.1.%pnpinfo: _HID=none _UID=0
dev.acpi_tz.1.%parent: acpi0
dev.attimer.0.%parent: acpi0
dev.attimer.1.%parent: acpi0
dev.atdma.0.%parent: acpi0
dev.fpupnp.0.%parent: acpi0
dev.atkbdc.0.%parent: acpi0
dev.psmcpnp.0.%parent: acpi0
dev.battery.0.%parent: acpi0
dev.acpi_acad.0.%desc: AC Adapter
dev.acpi_acad.0.%driver: acpi_acad
dev.acpi_acad.0.%location: handle=\_SB_.PCI0.LPC_.EC__.AC__
dev.acpi_acad.0.%pnpinfo: _HID=ACPI0003 _UID=0
dev.acpi_acad.0.%parent: acpi0
dev.acpi_ibm.0.%desc: IBM ThinkPad ACPI Extras
dev.acpi_ibm.0.%driver: acpi_ibm
dev.acpi_ibm.0.%location: handle=\_SB_.PCI0.LPC_.EC__.HKEY
dev.acpi_ibm.0.%pnpinfo: _HID=IBM0068 _UID=0
dev.acpi_ibm.0.%parent: acpi0
dev.acpi_ibm.0.initialmask: 2060
dev.acpi_ibm.0.availmask: 16777215
dev.acpi_ibm.0.events: 1
dev.acpi_ibm.0.eventmask: 16777215
dev.acpi_ibm.0.hotkey: 2471
dev.acpi_ibm.0.lcd_brightness: 0
dev.acpi_ibm.0.volume: 7
dev.acpi_ibm.0.mute: 1
dev.acpi_ibm.0.thinklight: 0
dev.acpi_ibm.0.bluetooth: 1
dev.acpi_ibm.0.wlan: 1
dev.acpi_ibm.0.fan_speed: 2598
dev.acpi_ibm.0.fan_level: 0
dev.acpi_ibm.0.fan: 1
dev.acpi_ibm.0.thermal: 42 39 28 48 50 -1 26 -1
dev.cpu.0.%parent: acpi0
dev.cpu.1.%parent: acpi0
dev.acpi_perf.0.%driver: acpi_perf
dev.acpi_perf.0.%parent: cpu0
dev.acpi_perf.1.%driver: acpi_perf
dev.acpi_perf.1.%parent: cpu1

---- sysctl -a | grep acpi: END ----

---- make.conf ----

CPUTYPE=	nocona
CFLAGS=		-O2 -pipe

---- make.conf: END ----




>How-To-Repeat:
/usr/sbin/acpiconf -s3 | -s4 | -s5

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From jkim at FreeBSD.org  Wed Dec 10 18:20:14 2008
From: jkim at FreeBSD.org (Jung-uk Kim)
Date: Wed Dec 10 18:20:26 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49358684.7010508@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org>
Message-ID: <200812102120.03788.jkim@FreeBSD.org>

On Tuesday 02 December 2008 02:03 pm, Alexander Motin wrote:
> Hi.
>
> Jung-uk Kim wrote:
> >> Here is problems I still have now:
> >>   - SMP kernel resume is not working, system reboots while doing
> >> acpi_wakeup_cpus();
> >
> > My dual-core CPU seems to resume okay but quite unstable.  Can
> > you try something like the following in amd64/mp_machdep.c and
> > tell me if it helps?
> >
> > ------------
> > @@ -57,6 +57,7 @@
> >  #include <vm/vm_extern.h>
> >
> >  #include <machine/apicreg.h>
> > +#include <machine/cpufunc.h>
> >  #include <machine/md_var.h>
> >  #include <machine/mp_watchdog.h>
> >  #include <machine/pcb.h>
> > @@ -1121,6 +1121,8 @@
> > 	int cpumask = PCPU_GET(cpumask);
> >
> > 	if (savectx2(&stopxpcbs[cpu])) {
> > +		/* Flush CPU cache. */
> > +		wbinvd();
> > 		/* Indicate that we are suspended. */
> > 		atomic_set_int(&stopped_cpus, cpumask);
> > 	} else {
> > ------------
>
> Wow, it works!
>
> I am writing this letter just after suspending/resuming my
> dual-core C2D system 4 times straight. Music plays, USB, SATA, all
> other hardware works fine. What kind of instability do you have?
>
> The only strange effect I have noticed was incorrect CPU time some
> processes got:
> %ps ax
>    PID  TT  STAT      TIME COMMAND
>     12  ??  WL   280503:38,05 [intr]
>   1430  ??  Ss   280503:38,34 icewm
>
> But I think it is more timer driver related then resume itself.
>
> > Thanks for the feedback!
>
> Many thanks to you! I hope this long-waited feature will be
> finished!

FYI, I uploaded a new patch with some fixes (against today's CURRENT):

http://people.freebsd.org/~jkim/amd64_suspend.diff

This patch should be feature complete but I'd say it is still 
considered experimental as it is not properly reviewed.

Now, some useful tips of the day for starters:

Tip #1: Try 'sysctl debug.acpi.suspend_bounce=1" first.  If it hangs, 
this patch won't do any good for you.

Tip #2: Suspend/resume several times in single user mode first to be 
safe.  I am sure you don't want to lose your data. ;-)

Tip #3: If keyboard LEDs blink (keyboard reset) but nothing is 
displayed on screen, try 'sysctl hw.acpi.reset_video=1' next time.

Tip #4: If #3 does not work for you, try 'vbetool post' (available 
from ports/sysutils/vbetool) next.  It works better in some cases.

Tip #5: With Xorg, it is always safe to suspend in console unless you 
have a hook in suspend script to do some magic.  When you switch to 
console by pressing Ctrl+Alt+F[1-8], Xorg driver will save GPU 
states.  After resume is complete, you can return to Xorg screen by 
pressing Alt-F9 later.  Then, Xorg driver should restore GPU states 
and screen.

Tip #6: If your mouse pointer does not move any more, try restarting 
moused by '/etc/rc.d/moused restart'.

Cheers,

Jung-uk Kim
From pyunyh at gmail.com  Wed Dec 10 18:49:43 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Wed Dec 10 18:49:51 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210140823.GF1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081210140823.GF1320@alf.bsdes.net>
Message-ID: <20081211024932.GC42370@cdnetworks.co.kr>

On Wed, Dec 10, 2008 at 03:08:24PM +0100, Victor Balada Diaz wrote:
 > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:

[...]

 > >  > >  > > It seems that your controller supports MSI so you can set a tunable
 > >  > >  > > hw.re.msi_disable to 0 to enable MSI. With MSI you can remove
 > >  > >  > > interrupt sharing(e.g. add hw.re.msi_disable="0" to
 > >  > >  > > /boot/loader.conf file.) However there were several issues on re(4)
 > >  > >  > > w.r.t MSI so it was off by default.
 > >  > >  > 
 > >  > >  > This is undocumented and with sysctl -a i can't find the tunable. Is this
 > >  > >  > a HEAD feature or it's also in 7.1 -BETA2? Should i add
 > >  > > 
 > >  > > Yeah it's an undocmented feature. But most drivers written by me
 > >  > > have similar kobs. Both HEAD and stable/7 including 7.1 BETA2 have
 > >  > > the tunable.
 > >  > 
 > >  > I think it could be great if you could document it or at least
 > >  > show it by default when you do sysctl -ad with a small description.
 > >  > 
 > > 
 > > If MSI worked as expected I would have documented it as I did
 > > in msk(4)/nfe(4)/ale(4)/age(4)/jme(4) etc.
 > > Using MSI on RealTek does not seem to stable. I tried hard to fix
 > > that but some users still reported watchdog timeouts. Working
 > > without documentation and hardware also made it hard to complete
 > > the work. This was the main reason why MSI was disabled on re(4).
 > 
 > What do you think about adding a note in the man page telling that
 > it's experimental and in some cases it could improve the situation
 > but in others it will give errors? 

Based on the your testing I have idea how to mitigate the missing
Tx completion interrupt. If all goes well re(4) could reliably take
advantage of MSI on RealTek controllers. If that miserably fail I
would do as you suggested.

 > > 
 > > I think re(4) in HEAD needs more testing. As you might know RealTek
 > > produced too many chipsets. :-(
 > 
 > Ok, i'll use the backported driver as it works better for me :-)
 > 
 > If i can help you testing any patches i'm more than welcome to do it.
 > 
 > Thanks a lot for your help Pyun YongHyeon.
 > 

You're welcome.
-- 
Regards,
Pyun YongHyeon
From linimon at FreeBSD.org  Wed Dec 10 20:50:00 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Dec 10 21:31:49 2008
Subject: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64]
Message-ID: <200812110449.mBB4nxYF060492@freefall.freebsd.org>

Synopsis: [ACPI] sleep broken on IBM/Lenovo T61 [amd64]

Responsible-Changed-From-To: freebsd-amd64->freebsd-acpi
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Dec 11 04:49:48 UTC 2008
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=129563
From pyunyh at gmail.com  Thu Dec 11 01:01:08 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Thu Dec 11 01:01:20 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081211081045.GJ1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
Message-ID: <20081211090056.GH42370@cdnetworks.co.kr>

On Thu, Dec 11, 2008 at 09:10:45AM +0100, Victor Balada Diaz wrote:
 > On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote:
 > > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
 > > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
 > > >  > Also i didn't see any problem with interfaces going up and down,
 > > >  > but that usually happen after some hours of uptime, so i'll let
 > > >  > you know if the error happens again.
 > > >  > 
 > > 
 > > After writing to the HD with dd for a few hours and using
 > > stress -i 10 -d 10 the machine lost connectivity. I waited until
 > > today to be sure if the machine hung, paniced or just lost network
 > > connectivity. I don't have local access or serial access, so this
 > > is the only way i could do it. I've seen in the logs during the
 > > night various messages of:
 > > 
 > > 
 > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout
 > > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN
 > > Dec 10 00:33:52 yac kernel: re0: link state changed to UP
 > > 
 > > The interface never recovered and i wasn't able to ping the machine
 > > until i rebooted. Nagios was checking all the time and no recovery
 > > happened.
 > > 
 > > The netstat -i in daily scripts shows just one Oerrs. I'm used to
 > > have a lot of them, but seems this time the card didn't recover from
 > > the only one. I also want to say that this is not a regression, as
 > > it happened before with 7.1 -BETA 2 code.
 > > 
 > > Is there anything more i can try?
 > 
 > Sorry it's too early in the morning and i thought today was 10
 > instead of 11. I don't even know the day i'm today.
 > 
 > Looking at today's log i see no link state changed messages
 > but i see this other messages that started happening more or
 > less at the same time i lost connectivity to the server:
 > 
 > Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN
 > Dec 10 18:20:32 yac kernel: re0: PHY read failed
 > 

I've reverted r185756 which caused GMII access issues on some
controllers. If you are brave enough to try beta code, you can
get latest re(4) in the following URL. Note, I don't have PCIe
based RealTek controllers so the code was not tested at all.

http://people.freebsd.org/~yongari/re/if_re.c
http://people.freebsd.org/~yongari/re/if_rlreg.h

-- 
Regards,
Pyun YongHyeon
From victor at bsdes.net  Wed Dec 10 23:57:10 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Thu Dec 11 04:35:33 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210120719.GK37837@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
Message-ID: <20081211075707.GH1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
> On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
>  > Also i didn't see any problem with interfaces going up and down,
>  > but that usually happen after some hours of uptime, so i'll let
>  > you know if the error happens again.
>  > 

After writing to the HD with dd for a few hours and using
stress -i 10 -d 10 the machine lost connectivity. I waited until
today to be sure if the machine hung, paniced or just lost network
connectivity. I don't have local access or serial access, so this
is the only way i could do it. I've seen in the logs during the
night various messages of:


Dec 10 00:33:49 yac kernel: re0: watchdog timeout
Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN
Dec 10 00:33:52 yac kernel: re0: link state changed to UP

The interface never recovered and i wasn't able to ping the machine
until i rebooted. Nagios was checking all the time and no recovery
happened.

The netstat -i in daily scripts shows just one Oerrs. I'm used to
have a lot of them, but seems this time the card didn't recover from
the only one. I also want to say that this is not a regression, as
it happened before with 7.1 -BETA 2 code.

Is there anything more i can try?

Regards.
-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From victor at bsdes.net  Thu Dec 11 00:00:27 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Thu Dec 11 04:35:40 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081210180559.GC58682@server.vk2pj.dyndns.org>
References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru>
	<20081210091107.GC1320@alf.bsdes.net>
	<A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>
	<20081210180559.GC58682@server.vk2pj.dyndns.org>
Message-ID: <20081211080026.GI1320@alf.bsdes.net>

On Thu, Dec 11, 2008 at 05:05:59AM +1100, Peter Jeremy wrote:
> On 2008-Dec-10 10:55:35 +0100, S?ren Schmidt <sos@freebsd.org> wrote:
> >And you will not use 64bit DMA even if the chipset supports it.  
> >However I have not seen any chipsets supporting this fail, YMMV as  
> >usual :)
> 
> There's a reference in wikipedia pointing to
> http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06694.html
> that claims the AMD/ATI SB600 lies about supporting 64-bit DMA in AHCI
> mode.  I have a SB600 but it doesn't have >4GB to test on.

I have 6 GB of RAM and can test patches, so once i'm done with the re(4)
side of things i'll try commenting the code Soren's suggested and see
if that improves the situation.

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From victor at bsdes.net  Thu Dec 11 00:10:47 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Thu Dec 11 04:35:48 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081211075707.GH1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
Message-ID: <20081211081045.GJ1320@alf.bsdes.net>

On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote:
> On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
> > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
> >  > Also i didn't see any problem with interfaces going up and down,
> >  > but that usually happen after some hours of uptime, so i'll let
> >  > you know if the error happens again.
> >  > 
> 
> After writing to the HD with dd for a few hours and using
> stress -i 10 -d 10 the machine lost connectivity. I waited until
> today to be sure if the machine hung, paniced or just lost network
> connectivity. I don't have local access or serial access, so this
> is the only way i could do it. I've seen in the logs during the
> night various messages of:
> 
> 
> Dec 10 00:33:49 yac kernel: re0: watchdog timeout
> Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN
> Dec 10 00:33:52 yac kernel: re0: link state changed to UP
> 
> The interface never recovered and i wasn't able to ping the machine
> until i rebooted. Nagios was checking all the time and no recovery
> happened.
> 
> The netstat -i in daily scripts shows just one Oerrs. I'm used to
> have a lot of them, but seems this time the card didn't recover from
> the only one. I also want to say that this is not a regression, as
> it happened before with 7.1 -BETA 2 code.
> 
> Is there anything more i can try?

Sorry it's too early in the morning and i thought today was 10
instead of 11. I don't even know the day i'm today.

Looking at today's log i see no link state changed messages
but i see this other messages that started happening more or
less at the same time i lost connectivity to the server:

Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN
Dec 10 18:20:32 yac kernel: re0: PHY read failed

Sorry for the noise.

Regards.
-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From victor at bsdes.net  Thu Dec 11 01:50:23 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Thu Dec 11 04:36:32 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081211090056.GH42370@cdnetworks.co.kr>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
Message-ID: <20081211095021.GL1320@alf.bsdes.net>

On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote:
> On Thu, Dec 11, 2008 at 09:10:45AM +0100, Victor Balada Diaz wrote:
>  > On Thu, Dec 11, 2008 at 08:57:07AM +0100, Victor Balada Diaz wrote:
>  > > On Wed, Dec 10, 2008 at 09:07:19PM +0900, Pyun YongHyeon wrote:
>  > > > On Wed, Dec 10, 2008 at 12:32:25PM +0100, Victor Balada Diaz wrote:
>  > > >  > Also i didn't see any problem with interfaces going up and down,
>  > > >  > but that usually happen after some hours of uptime, so i'll let
>  > > >  > you know if the error happens again.
>  > > >  > 
>  > > 
>  > > After writing to the HD with dd for a few hours and using
>  > > stress -i 10 -d 10 the machine lost connectivity. I waited until
>  > > today to be sure if the machine hung, paniced or just lost network
>  > > connectivity. I don't have local access or serial access, so this
>  > > is the only way i could do it. I've seen in the logs during the
>  > > night various messages of:
>  > > 
>  > > 
>  > > Dec 10 00:33:49 yac kernel: re0: watchdog timeout
>  > > Dec 10 00:33:49 yac kernel: re0: link state changed to DOWN
>  > > Dec 10 00:33:52 yac kernel: re0: link state changed to UP
>  > > 
>  > > The interface never recovered and i wasn't able to ping the machine
>  > > until i rebooted. Nagios was checking all the time and no recovery
>  > > happened.
>  > > 
>  > > The netstat -i in daily scripts shows just one Oerrs. I'm used to
>  > > have a lot of them, but seems this time the card didn't recover from
>  > > the only one. I also want to say that this is not a regression, as
>  > > it happened before with 7.1 -BETA 2 code.
>  > > 
>  > > Is there anything more i can try?
>  > 
>  > Sorry it's too early in the morning and i thought today was 10
>  > instead of 11. I don't even know the day i'm today.
>  > 
>  > Looking at today's log i see no link state changed messages
>  > but i see this other messages that started happening more or
>  > less at the same time i lost connectivity to the server:
>  > 
>  > Dec 10 18:20:32 yac kernel: re0: link state changed to DOWN
>  > Dec 10 18:20:32 yac kernel: re0: PHY read failed
>  > 
> 
> I've reverted r185756 which caused GMII access issues on some
> controllers. If you are brave enough to try beta code, you can
> get latest re(4) in the following URL. Note, I don't have PCIe
> based RealTek controllers so the code was not tested at all.
> 
> http://people.freebsd.org/~yongari/re/if_re.c
> http://people.freebsd.org/~yongari/re/if_rlreg.h

I've recompiled the kernel with the first file in sys/dev/re/
and the second one in sys/pci/. I'm still testing with MSI enabled.

So far tried rebooting using nextboot(8) (just in case i lost the
network card i could boot again) and the card seems to work
but i'll continue stress testing the machine with stress + dd +
iperf and see if i can take it down. I'll let you know how it goes.

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From mav at FreeBSD.org  Thu Dec 11 15:01:30 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Thu Dec 11 15:01:41 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <200812102120.03788.jkim@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<200812021243.08513.jkim@FreeBSD.org>
	<49358684.7010508@FreeBSD.org>
	<200812102120.03788.jkim@FreeBSD.org>
Message-ID: <49419BB9.8030408@FreeBSD.org>

Jung-uk Kim wrote:
> FYI, I uploaded a new patch with some fixes (against today's CURRENT):
> 
> http://people.freebsd.org/~jkim/amd64_suspend.diff

It is still working for me.

> This patch should be feature complete but I'd say it is still 
> considered experimental as it is not properly reviewed.

This comment looks stale:
/* Restore PAT and MTRRdefType. */
:)

-- 
Alexander Motin
From jkim at FreeBSD.org  Thu Dec 11 15:17:43 2008
From: jkim at FreeBSD.org (Jung-uk Kim)
Date: Thu Dec 11 15:17:54 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49419BB9.8030408@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<200812102120.03788.jkim@FreeBSD.org>
	<49419BB9.8030408@FreeBSD.org>
Message-ID: <200812111817.32334.jkim@FreeBSD.org>

On Thursday 11 December 2008 06:01 pm, Alexander Motin wrote:
> Jung-uk Kim wrote:
> > FYI, I uploaded a new patch with some fixes (against today's
> > CURRENT):
> >
> > http://people.freebsd.org/~jkim/amd64_suspend.diff
>
> It is still working for me.

Good.

> > This patch should be feature complete but I'd say it is still
> > considered experimental as it is not properly reviewed.
>
> This comment looks stale:
> /* Restore PAT and MTRRdefType. */

Corrected.

Thanks for the feedback!

Jung-uk Kim
From victor at bsdes.net  Fri Dec 12 04:13:12 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Fri Dec 12 04:47:26 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081211095021.GL1320@alf.bsdes.net>
References: <20081209185236.GA1320@alf.bsdes.net>
	<20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
	<20081211095021.GL1320@alf.bsdes.net>
Message-ID: <20081212121309.GM1320@alf.bsdes.net>

On Thu, Dec 11, 2008 at 10:50:21AM +0100, Victor Balada Diaz wrote:
> On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote:
> > 
> > I've reverted r185756 which caused GMII access issues on some
> > controllers. If you are brave enough to try beta code, you can
> > get latest re(4) in the following URL. Note, I don't have PCIe
> > based RealTek controllers so the code was not tested at all.
> > 
> > http://people.freebsd.org/~yongari/re/if_re.c
> > http://people.freebsd.org/~yongari/re/if_rlreg.h
> 
> I've recompiled the kernel with the first file in sys/dev/re/
> and the second one in sys/pci/. I'm still testing with MSI enabled.
> 
> So far tried rebooting using nextboot(8) (just in case i lost the
> network card i could boot again) and the card seems to work
> but i'll continue stress testing the machine with stress + dd +
> iperf and see if i can take it down. I'll let you know how it goes.

After a day of stress testing the machine haven't got errors, interrupt
storms or interface up/down problems. Everything seems fine.
I'll continue stress testing the machine during the weekend, but
i would say that this time it's fixed.

Seems lately there have been a lot of testing of this driver. Is
there any chance of it being on 7.1 or being MFCed after the release
to RELENG_7?

Thanks a lot.
Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From lapo at lapo.it  Fri Dec 12 04:29:40 2008
From: lapo at lapo.it (Lapo Luchini)
Date: Fri Dec 12 04:47:41 2008
Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64]
In-Reply-To: <20061231003901.GA76688@slackbox.xs4all.nl>
References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com>
	<20061231003901.GA76688@slackbox.xs4all.nl>
Message-ID: <ghtjp9$3j0$1@ger.gmane.org>

Roland Smith wrote:
> On Sat, Dec 30, 2006 at 05:10:08PM -0500, Siavosh Benabbas wrote:
>> Hi,
>> I know that this is brought up several time on this list, but I wanted to
>> run wine on my FreeBSD AMD64 machine.
>> I know that a 64-bit wine is nearly impossible but I thought that an i386
>> compilation should work.
> 
> You'd need a cross-compiler to start with. That's the easy part.
> 
> Then you'd need ports infrastructure to compile 32-bit ports on amd64.

Easiest approach to avoid that part seems to be seting up a full i386
jail inside the amd64 host, and install WINE normally from the ports.

>From man jail(8):

  host# D=/here/is/the/jail
  host# cd /usr/src
  host# mkdir -p $D
  host# make world DESTDIR=$D
  host# make distribution DESTDIR=$D
  host# mount -t devfs devfs $D/dev

But as suggested here <http://en.jnlin.org/2008/06/07/12/> I actually:

  host# make world distribution TARGET_ARCH=i386 TARGET=i386 DESTDIR=$D
  host# ln -s ld-elf.so.1 $D/libexec/ld-elf32.so.1

Then added IP alias for jail use, set up a unionfs over ports (to avoid
having them double) and can correctly login in the jail:

  host# ifconfig em0 inet $IP/32 alias
  host# mount -t unionfs -o noatime,below /usr/ports $D/usr/ports
  host# jail $D $HOSTNAME $IP /bin/tcsh

>From there I normally installed WINE:

  jail# cd /usr/ports/emulatos/wine
  jail# make install clean

?but then it just ?bus error? dumps on me? something to do with LDT:

  jail# winecfg
  Bus error (core dumped)
  jail# gdb `which wine-pthread` wine-pthread.core
  (gdb) bt
  #0  0x7df3b2e9 in wine_ldt_init_fs () from /usr/local/lib/libwine.so.1
  #1  0x7bf00fb3 in init_pthread_functions ()
  #2  0x7e36a81f in thread_init () from /usr/local/lib/wine/ntdll.dll.so
  #3  0x7e345d98 in __wine_process_init () from
  /usr/local/lib/wine/ntdll.dll.so
  #4  0x7df3bd74 in wine_init () from /usr/local/lib/libwine.so.1
  #5  0x7df571eb in wine_casemap_upper () from
  /usr/local/lib/libwine.so.1

-- 
Lapo Luchini - http://lapo.it/

?Beware of bugs in the above code; I have only proved it correct, not
tried it.? (Donald Knuth, 1977-03-22)

From kostikbel at gmail.com  Fri Dec 12 05:41:41 2008
From: kostikbel at gmail.com (Kostik Belousov)
Date: Fri Dec 12 05:41:59 2008
Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64]
In-Reply-To: <ghtjp9$3j0$1@ger.gmane.org>
References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com>
	<20061231003901.GA76688@slackbox.xs4all.nl>
	<ghtjp9$3j0$1@ger.gmane.org>
Message-ID: <20081212130631.GC2038@deviant.kiev.zoral.com.ua>

On Fri, Dec 12, 2008 at 01:00:41PM +0100, Lapo Luchini wrote:
> Roland Smith wrote:
> > On Sat, Dec 30, 2006 at 05:10:08PM -0500, Siavosh Benabbas wrote:
> >> Hi,
> >> I know that this is brought up several time on this list, but I wanted to
> >> run wine on my FreeBSD AMD64 machine.
> >> I know that a 64-bit wine is nearly impossible but I thought that an i386
> >> compilation should work.
> > 
> > You'd need a cross-compiler to start with. That's the easy part.
> > 
> > Then you'd need ports infrastructure to compile 32-bit ports on amd64.
> 
> Easiest approach to avoid that part seems to be seting up a full i386
> jail inside the amd64 host, and install WINE normally from the ports.
> 
> >From man jail(8):
> 
>   host# D=/here/is/the/jail
>   host# cd /usr/src
>   host# mkdir -p $D
>   host# make world DESTDIR=$D
>   host# make distribution DESTDIR=$D
>   host# mount -t devfs devfs $D/dev
> 
> But as suggested here <http://en.jnlin.org/2008/06/07/12/> I actually:
> 
>   host# make world distribution TARGET_ARCH=i386 TARGET=i386 DESTDIR=$D
>   host# ln -s ld-elf.so.1 $D/libexec/ld-elf32.so.1
This is not needed on recent HEAD or RELENG_7.

> 
> Then added IP alias for jail use, set up a unionfs over ports (to avoid
> having them double) and can correctly login in the jail:
> 
>   host# ifconfig em0 inet $IP/32 alias
>   host# mount -t unionfs -o noatime,below /usr/ports $D/usr/ports
>   host# jail $D $HOSTNAME $IP /bin/tcsh
> 
> >From there I normally installed WINE:
> 
>   jail# cd /usr/ports/emulatos/wine
>   jail# make install clean
> 
> ???but then it just ???bus error??? dumps on me??? something to do with LDT:
> 
>   jail# winecfg
>   Bus error (core dumped)
>   jail# gdb `which wine-pthread` wine-pthread.core
>   (gdb) bt
>   #0  0x7df3b2e9 in wine_ldt_init_fs () from /usr/local/lib/libwine.so.1
>   #1  0x7bf00fb3 in init_pthread_functions ()
>   #2  0x7e36a81f in thread_init () from /usr/local/lib/wine/ntdll.dll.so
>   #3  0x7e345d98 in __wine_process_init () from
>   /usr/local/lib/wine/ntdll.dll.so
>   #4  0x7df3bd74 in wine_init () from /usr/local/lib/libwine.so.1
>   #5  0x7df571eb in wine_casemap_upper () from
>   /usr/local/lib/libwine.so.1

Hmm, so you have a wine on amd64 and willingness to test ?
Please, try
http://people.freebsd.org/~kib/misc/amd64_ldt.2.patch
patch is against HEAD.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081212/c2e407c0/attachment.pgp
From kostikbel at gmail.com  Fri Dec 12 06:50:23 2008
From: kostikbel at gmail.com (Kostik Belousov)
Date: Fri Dec 12 06:50:35 2008
Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64]
In-Reply-To: <49427649.20006@lapo.it>
References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com>
	<20061231003901.GA76688@slackbox.xs4all.nl>
	<ghtjp9$3j0$1@ger.gmane.org>
	<20081212130631.GC2038@deviant.kiev.zoral.com.ua>
	<49427649.20006@lapo.it>
Message-ID: <20081212145015.GE2038@deviant.kiev.zoral.com.ua>

On Fri, Dec 12, 2008 at 03:33:45PM +0100, Lapo Luchini wrote:
> Kostik Belousov wrote:
> > Hmm, so you have a wine on amd64 and willingness to test ?
> > Please, try
> > http://people.freebsd.org/~kib/misc/amd64_ldt.2.patch
> > patch is against HEAD.
The right URL is
http://people.freebsd.org/~kib/misc/amd64_ctx.2.patch

> 
> Here in the office I've got a 7.0-RELEASE-p6 (updated with
> freebsd-update binary updates) and I'm not willing to test a patch
> against -CURRENT on it, but I may consider configuring a different host
> at home just for the sake of testing it??? is the patch simply against
> HEAD by accident or does really depend on changes that are not available
> in 7-STABLE?

I do not think that there is anything that prevents it from
being backported to 7, but probably it would require some handwork
for merge.

You can install only HEAD kernel on the 7 machine, it should work with
RELENG_7 world.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081212/8191055d/attachment.pgp
From lapo at lapo.it  Fri Dec 12 07:00:36 2008
From: lapo at lapo.it (Lapo Luchini)
Date: Fri Dec 12 07:00:43 2008
Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64]
In-Reply-To: <20081212130631.GC2038@deviant.kiev.zoral.com.ua>
References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com>
	<20061231003901.GA76688@slackbox.xs4all.nl>
	<ghtjp9$3j0$1@ger.gmane.org>
	<20081212130631.GC2038@deviant.kiev.zoral.com.ua>
Message-ID: <49427649.20006@lapo.it>

Kostik Belousov wrote:
> Hmm, so you have a wine on amd64 and willingness to test ?
> Please, try
> http://people.freebsd.org/~kib/misc/amd64_ldt.2.patch
> patch is against HEAD.

Here in the office I've got a 7.0-RELEASE-p6 (updated with
freebsd-update binary updates) and I'm not willing to test a patch
against -CURRENT on it, but I may consider configuring a different host
at home just for the sake of testing it? is the patch simply against
HEAD by accident or does really depend on changes that are not available
in 7-STABLE?

-- 
Lapo Luchini - http://lapo.it/

?Progress doesn't come from early risers ? progress is made by lazy men
looking for easier ways to do things.? (Robert A. Heinlein, 1973)
From avg at icyb.net.ua  Fri Dec 12 05:50:33 2008
From: avg at icyb.net.ua (Andriy Gapon)
Date: Fri Dec 12 10:31:44 2008
Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64]
In-Reply-To: <20081212130631.GC2038@deviant.kiev.zoral.com.ua>
References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com>	<20061231003901.GA76688@slackbox.xs4all.nl>	<ghtjp9$3j0$1@ger.gmane.org>
	<20081212130631.GC2038@deviant.kiev.zoral.com.ua>
Message-ID: <49426C23.10905@icyb.net.ua>

on 12/12/2008 15:06 Kostik Belousov said the following:
> 
> Hmm, so you have a wine on amd64 and willingness to test ?
> Please, try
> http://people.freebsd.org/~kib/misc/amd64_ldt.2.patch
> patch is against HEAD.

Kostik,

I also want to try your patch some time next week, but it seems that the
URL has mistake - I got 404.
Going to parent directory I see the following similarly named files:
amd64_ldt-pre.1.patch
amd64_ldt-pre.2.patch
amd64_ldt-pre.3.patch
amd64_ldt-pre.4.patch

-- 
Andriy Gapon
From pyunyh at gmail.com  Fri Dec 12 17:42:40 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Fri Dec 12 17:42:52 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081212121309.GM1320@alf.bsdes.net>
References: <20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
	<20081211095021.GL1320@alf.bsdes.net>
	<20081212121309.GM1320@alf.bsdes.net>
Message-ID: <20081213014229.GC51320@cdnetworks.co.kr>

On Fri, Dec 12, 2008 at 01:13:09PM +0100, Victor Balada Diaz wrote:
 > On Thu, Dec 11, 2008 at 10:50:21AM +0100, Victor Balada Diaz wrote:
 > > On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote:
 > > > 
 > > > I've reverted r185756 which caused GMII access issues on some
 > > > controllers. If you are brave enough to try beta code, you can
 > > > get latest re(4) in the following URL. Note, I don't have PCIe
 > > > based RealTek controllers so the code was not tested at all.
 > > > 
 > > > http://people.freebsd.org/~yongari/re/if_re.c
 > > > http://people.freebsd.org/~yongari/re/if_rlreg.h
 > > 
 > > I've recompiled the kernel with the first file in sys/dev/re/
 > > and the second one in sys/pci/. I'm still testing with MSI enabled.
 > > 
 > > So far tried rebooting using nextboot(8) (just in case i lost the
 > > network card i could boot again) and the card seems to work
 > > but i'll continue stress testing the machine with stress + dd +
 > > iperf and see if i can take it down. I'll let you know how it goes.
 > 
 > After a day of stress testing the machine haven't got errors, interrupt
 > storms or interface up/down problems. Everything seems fine.
 > I'll continue stress testing the machine during the weekend, but
 > i would say that this time it's fixed.
 > 

Thanks for testing!

 > Seems lately there have been a lot of testing of this driver. Is
 > there any chance of it being on 7.1 or being MFCed after the release
 > to RELENG_7?
 > 

It's too early to say MFC but I think MFC would be done after
releasing 7.1-RELEASE if all goes well.

-- 
Regards,
Pyun YongHyeon
From mav at FreeBSD.org  Sat Dec 13 12:06:52 2008
From: mav at FreeBSD.org (Alexander Motin)
Date: Sat Dec 13 12:07:04 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4944115C.5020403@lissyara.su>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su>
Message-ID: <494415D8.4090904@FreeBSD.org>

Alex Keda wrote:
> I trie it with my HP Compaq 6715s
> sleep OK, but after press power button, for wake up, i see blue screen, 
> and nothing... After hard reset, I have im /var/log/messages:
> 
> Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, 
> val 32768)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val 
> 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, 
> val 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, 
> val 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, 
> val 0)
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, 
> val 18)
> Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed!
> Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed
> Dec 13 22:35:31 acer kernel: bge0: initialization failure

Just interesting, how hostname "acer" related to "HP Compaq 6715s"? It's 
just a coincidence? :)

I have Acer TM6292 notebook with bge LAN. And my bge works fine after 
resume. The only specific of my notebook is that it's BIOS does not 
allocate resources for PCIe bridges. FreeBSD also unable to do it, so 
now I have to use dirty hack to initialize them. I think I have seen 
alike bge messages (but without reboot) when that hack was working only 
on boot, but not restoring PCIe bridges state on resume.

> Dec 13 22:40:52 acer savecore: reboot after panic: page fault
> Dec 13 22:40:52 acer savecore: writing core to vmcore.9

Core is good. May be it can be debugged?

-- 
Alexander Motin
From admin at lissyara.su  Sat Dec 13 12:22:36 2008
From: admin at lissyara.su (Alex Keda)
Date: Sat Dec 13 12:22:55 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4932F34C.1040804@FreeBSD.org>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org>
Message-ID: <4944115C.5020403@lissyara.su>

Alexander Motin ?????:
 > Hi.
 >
 > Alexander Motin wrote:
 >> Jung-uk Kim wrote:
 >>> I was working on suspend/resume support for amd64 and this is the
 >>> result.  It works with a modified QEMU (QEMU does not support S3) but
 >>> real boxes that I have don't seem to like it (e.g., broken BIOSes).
 >>> If there is someone interested in finishing it off or giving it a
 >>> try, the patch is here:
 >>>
 >>> http://people.freebsd.org/~jkim/amd64_suspend.diff
I trie it with my HP Compaq 6715s
sleep OK, but after press power button, for wake up, i see blue screen, 
and nothing... After hard reset, I have im /var/log/messages:


Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19
Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, 
val 32768)
Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val 
0xffffffff)
Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, 
val 0xffffffff)
Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, 
val 0xffffffff)
Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, 
val 0)
Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, 
val 18)
Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed!
Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed
Dec 13 22:35:31 acer kernel: bge0: initialization failure

and

Dec 13 22:40:52 acer savecore: reboot after panic: page fault
Dec 13 22:40:52 acer savecore: writing core to vmcore.9
=============
acer$ uname -a
FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: 
Sat Dec 13 22:29:48 MSK 2008 
lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console 
  amd64
From admin at lissyara.su  Sat Dec 13 12:41:05 2008
From: admin at lissyara.su (Alex Keda)
Date: Sat Dec 13 12:41:11 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4944115C.5020403@lissyara.su>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>	<4932F34C.1040804@FreeBSD.org>
	<4944115C.5020403@lissyara.su>
Message-ID: <49441DDE.2010706@lissyara.su>

Alex Keda ?????:
> Alexander Motin ?????:
>  > Hi.
>  >
>  > Alexander Motin wrote:
>  >> Jung-uk Kim wrote:
>  >>> I was working on suspend/resume support for amd64 and this is the
>  >>> result.  It works with a modified QEMU (QEMU does not support S3) but
>  >>> real boxes that I have don't seem to like it (e.g., broken BIOSes).
>  >>> If there is someone interested in finishing it off or giving it a
>  >>> try, the patch is here:
>  >>>
>  >>> http://people.freebsd.org/~jkim/amd64_suspend.diff
> I trie it with my HP Compaq 6715s
> sleep OK, but after press power button, for wake up, i see blue screen, 
sorry, read as 'dark screen' - no video...

From admin at lissyara.su  Sat Dec 13 12:53:27 2008
From: admin at lissyara.su (Alex Keda)
Date: Sat Dec 13 12:53:34 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4944115C.5020403@lissyara.su>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>	<4932F34C.1040804@FreeBSD.org>
	<4944115C.5020403@lissyara.su>
Message-ID: <494420C4.80702@lissyara.su>

Alex Keda ?????:
> Alexander Motin ?????:
>  > Hi.
>  >
>  > Alexander Motin wrote:
>  >> Jung-uk Kim wrote:
>  >>> I was working on suspend/resume support for amd64 and this is the
>  >>> result.  It works with a modified QEMU (QEMU does not support S3) but
>  >>> real boxes that I have don't seem to like it (e.g., broken BIOSes).
>  >>> If there is someone interested in finishing it off or giving it a
>  >>> try, the patch is here:
>  >>>
>  >>> http://people.freebsd.org/~jkim/amd64_suspend.diff
> I trie it with my HP Compaq 6715s
> sleep OK, but after press power button, for wake up, i see blue screen, 
> and nothing... After hard reset, I have im /var/log/messages:
> 
> 
> Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, 
> val 32768)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val 
> 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, 
> val 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, 
> val 0xffffffff)
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, 
> val 0)
> Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, 
> val 18)
> Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed!
> Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed
> Dec 13 22:35:31 acer kernel: bge0: initialization failure
> 
> and
> 
> Dec 13 22:40:52 acer savecore: reboot after panic: page fault
> Dec 13 22:40:52 acer savecore: writing core to vmcore.9
> =============
> acer$ uname -a
> FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: 
> Sat Dec 13 22:29:48 MSK 2008 
> lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console 
>  amd64

may be it useful...

acer# kgdb -q /boot/kernel/kernel vmcore.9
Reading symbols from /boot/kernel/sound.ko...Reading symbols from 
/boot/kernel/sound.ko.symbols...done.
done.
... skip ....
Loaded symbols for /boot/kernel/radeon.ko
Reading symbols from /boot/kernel/drm.ko...Reading symbols from 
/boot/kernel/drm.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/drm.ko
#0  doadump () at pcpu.h:196
196     pcpu.h: No such file or directory.
         in pcpu.h
(kgdb) bt
#0  doadump () at pcpu.h:196
#1  0xffffffff80528008 in boot (howto=260) at 
/usr/src/sys/kern/kern_shutdown.c:420
#2  0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at 
/usr/src/sys/kern/kern_shutdown.c:576
#3  0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, 
eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/trap.c:759
#4  0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, 
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675
#5  0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at 
/usr/src/sys/amd64/amd64/trap.c:444
#6  0xffffffff807c80ae in calltrap () at 
/usr/src/sys/amd64/amd64/exception.S:217
#7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at 
bus_if.h:46
#8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not 
available.
) at /usr/src/sys/kern/subr_bus.c:2953
#9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at 
/usr/src/sys/dev/ata/ata-all.c:713
#10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" 
is not available.
) at /usr/src/sys/dev/ata/ata-sata.c:69
#11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at 
/usr/src/sys/kern/subr_taskqueue.c:282
#12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is 
not available.
) at /usr/src/sys/kern/subr_taskqueue.c:403
#13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 
<taskqueue_thread_loop>, arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90)
     at /usr/src/sys/kern/kern_fork.c:821
#14 0xffffffff807c84be in fork_trampoline () at 
/usr/src/sys/amd64/amd64/exception.S:521
#15 0x0000000000000000 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x0000000000000000 in ?? ()
#18 0x0000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()
#20 0x0000000000000000 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000000 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000e8a000 in ?? ()
#40 0x000000000000000b in ?? ()
---Type <return> to continue, or q <return> to quit---
#41 0xffffffff80b4f880 in affinity ()
#42 0xffffffff80b4f880 in affinity ()
#43 0xffffff0001345720 in ?? ()
#44 0xfffffffe4005b240 in ?? ()
#45 0xfffffffe4005b1f8 in ?? ()
#46 0xffffff0001346720 in ?? ()
#47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, 
newtd=0xffffffff80b6b250, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/sched_ule.c:1848
Previous frame inner to this frame (corrupt stack?)
(kgdb) quit
=================================================
acer# dmesg | grep ata
atapci0: <ATI IXP600 SATA300 controller> port 
0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f 
mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports PM not supported
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: port not implemented
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: port not implemented
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: port not implemented
ata5: [ITHREAD]
atapci1: <ATI IXP600 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 
on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
acd0: DVDR <HL-DT-ST DVDRAM GSA-T20L/NC08> at ata0-master PIO4
ad4: 152627MB <TOSHIBA MK1646GSX LB114C> at ata2-master SATA300
cd0 at ata0 bus 0 target 0 lun 0
acer#










From nate at root.org  Sat Dec 13 13:04:55 2008
From: nate at root.org (Nate Lawson)
Date: Sat Dec 13 13:27:11 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <494420C4.80702@lissyara.su>
References: <1224616985.00027652.1224606603@10.7.7.3>	<1224728582.00028075.1224715806@10.7.7.3>	<4932F34C.1040804@FreeBSD.org>	<4944115C.5020403@lissyara.su>
	<494420C4.80702@lissyara.su>
Message-ID: <49442375.4010401@root.org>

Alex Keda wrote:
>> Dec 13 22:40:52 acer savecore: reboot after panic: page fault
>> Dec 13 22:40:52 acer savecore: writing core to vmcore.9
>> =============
>> acer$ uname -a
>> FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT
>> #0: Sat Dec 13 22:29:48 MSK 2008
>> lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console
>>  amd64
> 
> may be it useful...
> 
> acer# kgdb -q /boot/kernel/kernel vmcore.9
> Reading symbols from /boot/kernel/sound.ko...Reading symbols from
> /boot/kernel/sound.ko.symbols...done.
> done.
> ... skip ....
> Loaded symbols for /boot/kernel/radeon.ko
> Reading symbols from /boot/kernel/drm.ko...Reading symbols from
> /boot/kernel/drm.ko.symbols...done.
> done.
> Loaded symbols for /boot/kernel/drm.ko
> #0  doadump () at pcpu.h:196
> 196     pcpu.h: No such file or directory.
>         in pcpu.h
> (kgdb) bt
> #0  doadump () at pcpu.h:196
> #1  0xffffffff80528008 in boot (howto=260) at
> /usr/src/sys/kern/kern_shutdown.c:420
> #2  0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at
> /usr/src/sys/kern/kern_shutdown.c:576
> #3  0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720,
> eva=Variable "eva" is not available.
> ) at /usr/src/sys/amd64/amd64/trap.c:759
> #4  0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20,
> usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675
> #5  0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at
> /usr/src/sys/amd64/amd64/trap.c:444
> #6  0xffffffff807c80ae in calltrap () at
> /usr/src/sys/amd64/amd64/exception.S:217
> #7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at
> bus_if.h:46
> #8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not
> available.
> ) at /usr/src/sys/kern/subr_bus.c:2953
> #9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at
> /usr/src/sys/dev/ata/ata-all.c:713
> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context"
> is not available.
> ) at /usr/src/sys/dev/ata/ata-sata.c:69
> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at
> /usr/src/sys/kern/subr_taskqueue.c:282
> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is
> not available.
> ) at /usr/src/sys/kern/subr_taskqueue.c:403
> #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790
> <taskqueue_thread_loop>, arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90)
>     at /usr/src/sys/kern/kern_fork.c:821
> #14 0xffffffff807c84be in fork_trampoline () at
> /usr/src/sys/amd64/amd64/exception.S:521
> #15 0x0000000000000000 in ?? ()

> acer# dmesg | grep ata
> atapci0: <ATI IXP600 SATA300 controller> port
> 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f
> mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0
> atapci0: [ITHREAD]
> atapci0: AHCI Version 01.10 controller with 4 ports PM not supported
> ata2: <ATA channel 0> on atapci0
> ata2: [ITHREAD]
> ata3: <ATA channel 1> on atapci0
> ata3: port not implemented
> ata3: [ITHREAD]
> ata4: <ATA channel 2> on atapci0
> ata4: port not implemented
> ata4: [ITHREAD]
> ata5: <ATA channel 3> on atapci0
> ata5: port not implemented
> ata5: [ITHREAD]
> atapci1: <ATI IXP600 UDMA133 controller> port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1
> on pci0
> ata0: <ATA channel 0> on atapci1
> ata0: [ITHREAD]
> acd0: DVDR <HL-DT-ST DVDRAM GSA-T20L/NC08> at ata0-master PIO4
> ad4: 152627MB <TOSHIBA MK1646GSX LB114C> at ata2-master SATA300
> cd0 at ata0 bus 0 target 0 lun 0

ATA should be disabling its SATA PHY task during suspend, then
re-enabling it after resume. Looks like it doesn't do this.

-- 
Nate
From linimon at FreeBSD.org  Sun Dec 14 17:55:35 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Sun Dec 14 18:29:27 2008
Subject: amd64/129515: apache activemq always cause system reboot
Message-ID: <200812150155.mBF1tZ1U035180@freefall.freebsd.org>

Synopsis: apache activemq always cause system reboot

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Mon Dec 15 01:55:16 UTC 2008
State-Changed-Why: 
Apparently fixed by an upgrade to 6.4.

http://www.freebsd.org/cgi/query-pr.cgi?pr=129515
From bu7cher at yandex.ru  Sun Dec 14 21:30:13 2008
From: bu7cher at yandex.ru (Andrey V. Elsukov)
Date: Mon Dec 15 08:19:15 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <49442375.4010401@root.org>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su>
	<494420C4.80702@lissyara.su> <49442375.4010401@root.org>
Message-ID: <4945EB56.1060608@yandex.ru>

Nate Lawson wrote:
>> #7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at
>> bus_if.h:46
>> #8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not
>> available.
>> ) at /usr/src/sys/kern/subr_bus.c:2953
>> #9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at
>> /usr/src/sys/dev/ata/ata-all.c:713
>> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context"
>> is not available.
>> ) at /usr/src/sys/dev/ata/ata-sata.c:69
>> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at
>> /usr/src/sys/kern/subr_taskqueue.c:282
>> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is
>> not available.
> 
> ATA should be disabling its SATA PHY task during suspend, then
> re-enabling it after resume. Looks like it doesn't do this.

It seems that resuming of ATA controller is already done.
AHCI interrupts are enabled and PHY state was changed.
And task are doing attach of hot-plugged device..
So, Alex, can you show output of a kgdb command:
(kgdb) p "%s", msgbufp->msg_ptr

-- 
WBR, Andrey V. Elsukov
From victor at bsdes.net  Mon Dec 15 01:02:10 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Mon Dec 15 08:25:14 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081212121309.GM1320@alf.bsdes.net>
References: <20081210061226.GC37837@cdnetworks.co.kr>
	<20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
	<20081211095021.GL1320@alf.bsdes.net>
	<20081212121309.GM1320@alf.bsdes.net>
Message-ID: <20081215090207.GN1320@alf.bsdes.net>

On Fri, Dec 12, 2008 at 01:13:09PM +0100, Victor Balada Diaz wrote:
> On Thu, Dec 11, 2008 at 10:50:21AM +0100, Victor Balada Diaz wrote:
> > On Thu, Dec 11, 2008 at 06:00:56PM +0900, Pyun YongHyeon wrote:
> > > 
> > > I've reverted r185756 which caused GMII access issues on some
> > > controllers. If you are brave enough to try beta code, you can
> > > get latest re(4) in the following URL. Note, I don't have PCIe
> > > based RealTek controllers so the code was not tested at all.
> > > 
> > > http://people.freebsd.org/~yongari/re/if_re.c
> > > http://people.freebsd.org/~yongari/re/if_rlreg.h
> > 
> > I've recompiled the kernel with the first file in sys/dev/re/
> > and the second one in sys/pci/. I'm still testing with MSI enabled.
> > 
> > So far tried rebooting using nextboot(8) (just in case i lost the
> > network card i could boot again) and the card seems to work
> > but i'll continue stress testing the machine with stress + dd +
> > iperf and see if i can take it down. I'll let you know how it goes.
> 
> After a day of stress testing the machine haven't got errors, interrupt
> storms or interface up/down problems. Everything seems fine.
> I'll continue stress testing the machine during the weekend, but
> i would say that this time it's fixed.

Stopped stress testing this morning. After all the weekend testing
seems the re(4) problems were fixed. No single interface up/down error.
netstat -i reports no errors and everything is fine. Thanks a lot!

I'm going to deploy the patches on our production machines.

I've been able to trigger interrupt storms with ATA code, though.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From victor at bsdes.net  Mon Dec 15 01:07:12 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Mon Dec 15 08:25:26 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>
References: <20081209185236.GA1320@alf.bsdes.net> <493F84A4.1080308@yandex.ru>
	<20081210091107.GC1320@alf.bsdes.net>
	<A8284393-C4E8-4E7D-9ADF-F8270C354E13@FreeBSD.ORG>
Message-ID: <20081215090710.GO1320@alf.bsdes.net>

On Wed, Dec 10, 2008 at 10:55:35AM +0100, S?ren Schmidt wrote:
> On 10Dec, 2008, at 10:11 , Victor Balada Diaz wrote:
> >
> >Thanks for explaining me what the flags do. I'm not skilled enough  
> >to create
> >the DMA quirks but if you could give me some patches i'll test them.  
> >Also
> >if you have any other idea on what could i test or how can i debug  
> >this
> >it would be more than welcome.
> 
> 
> Comment out the following two lines in ata_ahci_dmainit():
> 
>         if (ATA_INL(ctlr->r_res2, ATA_AHCI_CAP) & ATA_AHCI_CAP_64BIT)
>             ch->dma->max_address = BUS_SPACE_MAXADDR;
> 
> And you will not use 64bit DMA even if the chipset supports it.  
> However I have not seen any chipsets supporting this fail, YMMV as  
> usual :)
> 
Hello S?ren,

I'm triggering interrupt storms with this chipset after a few
days of stressing the HD calling sysutils/stress with stress -d 10 -i 10
and in other term, doing: 

 while true; do dd if=/dev/zero of=BAH bs=1M count=1024; done;

Right now, as reported by systat -vmstat i have 578k interrupts in atapci
and the machine is idle. Do you have any idea on how could i debug
this? any advice would be much more than welcome.

Thanks a lot.
Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From bugmaster at FreeBSD.org  Mon Dec 15 03:06:48 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Dec 15 08:25:40 2008
Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org
Message-ID: <200812151106.mBFB6lOG004250@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/129488 amd64      [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: 
o amd64/129426 amd64      [panic] FreeBSD 7.0 crash after subdiskXX: detached
o amd64/129315 amd64      [boot] amd64 motherboard: Intel DG965WH motherboard co
o amd64/129238 amd64      [panic] System randomly panics
f amd64/128978 amd64      [install] FreeBSD 6.3 64-bit  panics at boot time duri
o amd64/128810 amd64      AMD 64 port installation
o amd64/128765 amd64      [install] Install CD loads to Install choices but stop
o amd64/128686 amd64      [ata] can't detect SATA Disk on 8.0-Current with NF550
o amd64/128524 amd64      No geom documentation for loading gjournal
o amd64/128263 amd64      [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a
o amd64/128259 amd64      csh(1): "`" crashes csh
o amd64/128236 amd64      portsdb -Uu Indexing error
f kern/128102  amd64      AsusRock 939N68PV-GLAN not recognized
o amd64/127787 amd64      [lor] 3 lock LOR in recent CURRENT
o amd64/127640 amd64      GCC will not build shared libraries with -fprofile-gen
o amd64/127492 amd64      [zfs] System hang on ZFS input-output
o amd64/127484 amd64      [timecounters] Drift problem with FreeBSD 7.0 and 7.1 
o amd64/127451 amd64      [scheduler] incorrect load on quad core
o amd64/127397 amd64      [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI
s amd64/127276 amd64      ldd(1) invokes linux yes
o amd64/127129 amd64      mdconfig(8) is core dumping with Segmentation Fault 11
f amd64/125943 amd64      Serial Consoles do not work on amd64 freebsd
o amd64/125873 amd64      [smbd] [panic] Repeated kernel panics, trap 12 page fa
o amd64/125002 amd64      [install] amd64, SATA hard disks not detected
o amd64/124432 amd64      [panic] 7.0-STABLE panic: invalbuf: dirty bufs
o amd64/124134 amd64      [kernel] The kernel doesn't follow the calling convent
o amd64/123562 amd64      [install] FreeBSD amd64 not installs
o amd64/123520 amd64      [ahd] unable to boot from net while using ahd
o amd64/123456 amd64      fstat(1): /usr/bin/fstat shows error messages and hang
f amd64/123275 amd64      [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re
o kern/122782  amd64      [modules] accf_http.ko kernel module is not loadable
o amd64/122695 amd64      [cpufreq] Lack of cpufreq control using amd64 eith cor
o amd64/122624 amd64      unusable minimal installation of FreeBSD-7.0
o amd64/122549 amd64      7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial 
o amd64/122468 amd64      Compile problems after upgrading to 7.0
o amd64/122174 amd64      [panic] 7.0 no longer includes "device atpic" so fails
o amd64/121590 amd64      [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet
o amd64/121439 amd64      [boot] Installation of FreeBSD 7.0 fails: ACPI problem
o amd64/120202 amd64      [amd64] [patch] [panic] kernel panic at start_all_aps,
o amd64/119936 amd64      [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis
o amd64/119591 amd64      [amd64] [patch] time_t on 64-bit architecture
o amd64/117418 amd64      [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh
o amd64/117316 amd64      [acpi] ACPI lockups on SuperMicro motherboard
o amd64/117296 amd64      [ata] I don`t see second SATA IDE on VIA VT8237A
a amd64/117186 amd64      [modules] kldload Unsupported file type on STABLE amd6
s amd64/116689 amd64      [request] support for MSI K9MM-V
f amd64/116670 amd64      [ata] onboard SATA RAID1 controllers not supported for
o amd64/116620 amd64      [hang] ifconfig spins when creating carp(4) device on 
o amd64/116322 amd64      [panic] At start fsck on current, the system panics
o amd64/116159 amd64      [panic] Panic while debugging on CURRENT
s amd64/115815 amd64      [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp
o amd64/115581 amd64      [Makefile] [patch] -mfancy-math-387 has no effect
o amd64/115194 amd64      LCD screen remains blank after Dell XPS M1210 lid is c
o amd64/114270 amd64      [cpufreq] cpufreq doesnt work when compiled in to kern
o amd64/114111 amd64      [nfs] System crashes while writing on NFS-mounted shar
f amd64/113021 amd64      [re] ASUS M2A-VM onboard NIC does not work
o amd64/112222 amd64      [libc] 32-bit libc incorrectly converts some FP number
f amd64/111992 amd64      [boot] BTX failed - HP Laptop dv2315nr
o amd64/110655 amd64      [threads] 32 bit threaded applications crash on amd64 
o amd64/110599 amd64      [geli] geli attach to gmirror device hangs and cannot 
s amd64/108861 amd64      [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work
o amd64/106186 amd64      [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p
f amd64/105629 amd64      [re] TrendNet TEG-BUSR 10/100/1000 disables itself on 
f amd64/105531 amd64      [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does
f amd64/105514 amd64      [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv
o amd64/102716 amd64      ex with no argument in an xterm gets SIGSEGV
o amd64/97337  amd64      [dri] xorg reboots system if dri module is enabled
o amd64/95888  amd64      [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP 
f amd64/94989  amd64      [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64)
o amd64/94677  amd64      [panic] panic in amd64 install at non-root user creati
o amd64/93961  amd64      [busdma] Problem in bounce buffer handling in sys/amd6
o amd64/92337  amd64      [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff
f amd64/91492  amd64      [boot] BTX halted
o amd64/91405  amd64      [asr] [panic] Kernel panic caused by asr on 6.0-amd64 
o amd64/89501  amd64      [install] System crashes on install using ftp on local
o amd64/88790  amd64      [panic] kernel panic on first boot (after the FreeBSD 
o amd64/88568  amd64      [panic] 6.0-RELEASE install cd does not boot with usb 
o amd64/87689  amd64      [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE
o amd64/87316  amd64      [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6
o amd64/87305  amd64      [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in
f amd64/87258  amd64      [smp] [boot] cannot boot with SMP and Areca ARC-1160 r
f amd64/86080  amd64      [radeon] [hang] radeon DRI causes system hang on amd64
s amd64/85273  amd64      [install] FreeBSD (NetBSD or OpenBSD) not install on l
o amd64/78406  amd64      [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys
o amd64/76136  amd64      [hang] system halts before reboot
o amd64/74747  amd64      [panic] System panic on shutdown when process will not
o amd64/73322  amd64      [msdosfs] [hang] unarchiving /etc to msdosfs locks up 

87 problems total.

From tom.benda at dailyevergreen.com  Mon Dec 15 14:00:20 2008
From: tom.benda at dailyevergreen.com (Tom Benda)
Date: Mon Dec 15 14:41:57 2008
Subject: amd64/129667: Elitegroup A780GM-A IDE controller not recognized in
	6.4 amd64
Message-ID: <200812152154.mBFLsc6N025366@www.freebsd.org>


>Number:         129667
>Category:       amd64
>Synopsis:       Elitegroup A780GM-A IDE controller not recognized in 6.4 amd64
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 15 22:00:14 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Tom Benda
>Release:        6.4 amd64
>Organization:
Washington State University Student Publications
>Environment:
>Description:
"No disks found" message on IDE controller for an Elitegroup A780GM-A motherboard. 

Running FreeBSD 6.4 amd64 CD release.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From pyunyh at gmail.com  Mon Dec 15 23:49:00 2008
From: pyunyh at gmail.com (Pyun YongHyeon)
Date: Mon Dec 15 23:49:13 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081216071919.GR1320@alf.bsdes.net>
References: <20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
	<20081211095021.GL1320@alf.bsdes.net>
	<20081212121309.GM1320@alf.bsdes.net>
	<20081215090207.GN1320@alf.bsdes.net>
	<20081216071919.GR1320@alf.bsdes.net>
Message-ID: <20081216074851.GD62771@cdnetworks.co.kr>

On Tue, Dec 16, 2008 at 08:19:19AM +0100, Victor Balada Diaz wrote:
 > On Mon, Dec 15, 2008 at 10:02:07AM +0100, Victor Balada Diaz wrote:
 > > Stopped stress testing this morning. After all the weekend testing
 > > seems the re(4) problems were fixed. No single interface up/down error.
 > > netstat -i reports no errors and everything is fine. Thanks a lot!
 > > 
 > > I'm going to deploy the patches on our production machines.
 > > 
 > > I've been able to trigger interrupt storms with ATA code, though.
 > 
 > After deploying it in various machines this night i've found in the
 > logs messages like this one:
 > 
 > re0: watchdog timeout (missed Tx interrupts) -- recovering
 > 
 > I know you told me this is harmless, so this is just so you

Yes, it's not real watchdog timeout as long as re(4) still works
correctly.

 > know it's happening.
 > 

Ok. I'll update re(4) when I find spare time.

-- 
Regards,
Pyun YongHyeon
From admin at lissyara.su  Tue Dec 16 01:07:06 2008
From: admin at lissyara.su (Alex Keda)
Date: Tue Dec 16 01:07:16 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4945EB56.1060608@yandex.ru>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su>
	<494420C4.80702@lissyara.su> <49442375.4010401@root.org>
	<4945EB56.1060608@yandex.ru>
Message-ID: <49476FB6.1020705@lissyara.su>

Andrey V. Elsukov пишет:
> Nate Lawson wrote:
>>> #7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at
>>> bus_if.h:46
>>> #8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not
>>> available.
>>> ) at /usr/src/sys/kern/subr_bus.c:2953
>>> #9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at
>>> /usr/src/sys/dev/ata/ata-all.c:713
>>> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable 
>>> "context"
>>> is not available.
>>> ) at /usr/src/sys/dev/ata/ata-sata.c:69
>>> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at
>>> /usr/src/sys/kern/subr_taskqueue.c:282
>>> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is
>>> not available.
>>
>> ATA should be disabling its SATA PHY task during suspend, then
>> re-enabling it after resume. Looks like it doesn't do this.
>
> It seems that resuming of ATA controller is already done.
> AHCI interrupts are enabled and PHY state was changed.
> And task are doing attach of hot-plugged device..
> So, Alex, can you show output of a kgdb command:
> (kgdb) p "%s", msgbufp->msg_ptr
>
big output.
see attached file

-------------- next part --------------
Script started on Tue Dec 16 12:03:21 2008
HP# kgdb -q /boot/kernel/kernel vmcore.9

Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/snd_hda.ko
Reading symbols from /boot/kernel/umodem.ko...Reading symbols from /boot/kernel/umodem.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/umodem.ko
Reading symbols from /boot/kernel/acpi_video.ko...Reading symbols from /boot/kernel/acpi_video.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_video.ko
Reading symbols from /boot/kernel/atapicam.ko...Reading symbols from /boot/kernel/atapicam.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/atapicam.ko
Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols from /boot/kernel/acpi_aiboost.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_aiboost.ko
Reading symbols from /boot/kernel/acpi_dock.ko...Reading symbols from /boot/kernel/acpi_dock.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_dock.ko
Reading symbols from /boot/kernel/ng_bt3c.ko...Reading symbols from /boot/kernel/ng_bt3c.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_bt3c.ko
Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/netgraph.ko
Reading symbols from /boot/kernel/ng_btsocket.ko...Reading symbols from /boot/kernel/ng_btsocket.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_btsocket.ko
Reading symbols from /boot/kernel/ng_bluetooth.ko...Reading symbols from /boot/kernel/ng_bluetooth.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_bluetooth.ko
Reading symbols from /boot/kernel/ng_ubt.ko...Reading symbols from /boot/kernel/ng_ubt.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_ubt.ko
Reading symbols from /boot/kernel/ubtbcmfw.ko...Reading symbols from /boot/kernel/ubtbcmfw.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ubtbcmfw.ko
Reading symbols from /boot/kernel/ng_l2cap.ko...Reading symbols from /boot/kernel/ng_l2cap.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_l2cap.ko
Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from /boot/kernel/iicbb.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbb.ko
Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from /boot/kernel/iicbus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbus.ko
Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /boot/kernel/tmpfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/tmpfs.ko
Reading symbols from /boot/kernel/ng_hci.ko...Reading symbols from /boot/kernel/ng_hci.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_hci.ko
Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_socket.ko
Reading symbols from /boot/kernel/ipfw.ko...Reading symbols from /boot/kernel/ipfw.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ipfw.ko
Reading symbols from /boot/kernel/vkbd.ko...Reading symbols from /boot/kernel/vkbd.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/vkbd.ko
Reading symbols from /usr/local/modules/fuse.ko...done.
Loaded symbols for /usr/local/modules/fuse.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/radeon.ko...Reading symbols from /boot/kernel/radeon.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/radeon.ko
Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/drm.ko
#0  doadump () at pcpu.h:196
196	pcpu.h: No such file or directory.
	in pcpu.h
(kgdb) bt
#0  doadump () at pcpu.h:196
#1  0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420
#2  0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576
#3  0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/trap.c:759
#4  0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675
#5  0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444
#6  0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217
#7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at bus_if.h:46
#8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available.
) at /usr/src/sys/kern/subr_bus.c:2953
#9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713
#10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available.
) at /usr/src/sys/dev/ata/ata-sata.c:69
#11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282
#12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available.
) at /usr/src/sys/kern/subr_taskqueue.c:403
#13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 <taskqueue_thread_loop>, arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821
#14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521
#15 0x0000000000000000 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x0000000000000000 in ?? ()
#18 0x0000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()
#20 0x0000000000000000 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000000 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000e8a000 in ?? ()
#40 0x000000000000000b in ?? ()
#41 0xffffffff80b4f880 in affinity ()
#42 0xffffffff80b4f880 in affinity ()
#43 0xffffff0001345720 in ?? ()
#44 0xfffffffe4005b240 in ?? ()
#45 0xfffffffe4005b1f8 in ?? ()
#46 0xffffff0001346720 in ?? ()
#47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/sched_ule.c:1848
Previous frame inner to this frame (corrupt stack?)
(kgdb) 
#0  doadump () at pcpu.h:196
#1  0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420
#2  0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576
#3  0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/trap.c:759
#4  0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675
#5  0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444
#6  0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217
#7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at bus_if.h:46
#8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available.
) at /usr/src/sys/kern/subr_bus.c:2953
#9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713
#10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available.
) at /usr/src/sys/dev/ata/ata-sata.c:69
#11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282
#12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available.
) at /usr/src/sys/kern/subr_taskqueue.c:403
#13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 <taskqueue_thread_loop>, arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821
#14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521
#15 0x0000000000000000 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x0000000000000000 in ?? ()
#18 0x0000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()
#20 0x0000000000000000 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000000 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000e8a000 in ?? ()
#40 0x000000000000000b in ?? ()
#41 0xffffffff80b4f880 in affinity ()
#42 0xffffffff80b4f880 in affinity ()
#43 0xffffff0001345720 in ?? ()
#44 0xfffffffe4005b240 in ?? ()
#45 0xfffffffe4005b1f8 in ?? ()
#46 0xffffff0001346720 in ?? ()
#47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/sched_ule.c:1848
(kgdb) printf "%s", msgbufp->msg_ptr
led, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>.
<118>Shutting down local packages:powernow0: set freq failed, err 6
<118> rtc00001 allow ip from any to any
<118>[: =: unexpected operator
<118>.
<118>Stopping cron.
<118>Stopping sshd.
<118>Waiting for PIDS: 1281powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>.
<118>Stopping cupsd.
<118>Waiting for PIDS: 1220powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>.
<118>Stopping exim.
powernow0: set freq failed, err 6
<118>Stopping powerd.
powernow1: set freq failed, err 6
powernow1: set freq failed, err 6
<118>sysctl: : Stopping fusefs.
<118>Stopping bthidd.
<118>Waiting for PIDS: 1079.
<118>Stopping hcsecd.
<118>Stopping named.
<118>Waiting for PIDS: 930.
<118>Stopping devd.
<6>pid 1396 (hald), uid 560: exited on signal 11
<118>Writing entropy file:.
<118>.
<118>Dec 13 22:33:35 acer syslogd: exiting on signal 15
---Type <return> to continue, or q <return> to quit---
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiti
nSgy n(cmianxg  6d0i sskesc,o nvdnso)d efso rr esmyasitneimn gp.r.o.ce5s s `syncer' to stop...2 1 1 0 0 done
All buffers synced.
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-CURRENT #0: Sat Dec 13 22:29:48 MSK 2008
    lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1995.01-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x60f82  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
  Cores per package: 2
usable memory = 1998295040 (1905 MB)
avail memory  = 1929797632 (1840 MB)
ACPI APIC Table: <HP     0944    >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ACPI Error (tbfadt-0516): 32/64X address mismatch in "Pm2ControlBlock": [    8800] [       0    8100], using 64X [20070320]
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <HPQOEM SLIC-MPC> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
unknown: I/O range not supported
acpi0: reservation of 0, 8000000 (3) failed
acpi0: reservation of 100000, fff00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x11> port 0x62,0x66 on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1
acpi_video0: <ACPI video extension> on vgapci0
pcib2: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci16: <ACPI PCI bus> on pcib2
bge0: <Broadcom BCM5906 A2, ASIC rev. 0xc002> mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16
miibus0: <MII bus> on bge0
brgphy0: <BCM5906 10/100baseTX PHY> PHY 1 on miibus0
---Type <return> to continue, or q <return> to quit---
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bge0: Ethernet address: 00:1f:29:89:38:f3
bge0: [ITHREAD]
pcib3: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci32: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci48: <ACPI PCI bus> on pcib4
pci48: <network> at device 0.0 (no driver attached)
atapci0: <ATI IXP600 SATA300 controller> port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports PM not supported
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: port not implemented
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: port not implemented
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: port not implemented
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: <OHCI (generic) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
---Type <return> to continue, or q <return> to quit---
usb3: OHCI version 1.0, legacy support
usb3: <OHCI (generic) USB controller> on ohci3
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ohci4: <OHCI (generic) USB controller> mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: <OHCI (generic) USB controller> on ohci4
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci0
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 10 ports with 10 removable, self powered
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
hdac0: <ATI SB600 High Definition Audio Controller> irq 16 at device 20.2 on pci0
hdac0: HDA Driver Revision: 20081123_0118
hdac0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib5: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci2: <ACPI PCI bus> on pcib5
cbb0: <RF5C476 PCI-CardBus Bridge> mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [FILTER]
battery0: <ACPI Control Method Battery> on acpi0
battery1: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_button0: <Sleep Button> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x73 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
---Type <return> to continue, or q <return> to quit---
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
powernow1: <PowerNow! K8> on cpu1
orm0: <ISA Option ROM> at iomem 0xd0000-0xd0fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: cannot reserve I/O port range
ubt0: <Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.00, addr 2> on uhub0
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=10, buffer size=640
ums0: <Logitech Optical USB Mouse, class 0/0, rev 2.00/3.40, addr 2> on uhub1
ums0: 3 buttons and Z dir.
Timecounters tick every 1.000 msec
acd0: DVDR <HL-DT-ST DVDRAM GSA-T20L/NC08> at ata0-master PIO4
ad4: 152627MB <TOSHIBA MK1646GSX LB114C> at ata2-master SATA300
hdac0: HDA Codec #0: Analog Devices AD1981HD
hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown)
pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s1a
<118>Entropy harvesting: interrupts ethernet point_to_point kickstart.
<118>/dev/ad4s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
<118>/dev/ad4s1a: clean, 52516070 free (100286 frags, 6551973 blocks, 0.1% fragmentation)
WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD.
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
cd0 at ata0 bus 0 target 0 lun 0
cd0: <HL-DT-ST DVDRAM GSA-T20L NC08> Removable CD-ROM SCSI-0 device 
cd0: 16.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
<118>Starting Network: lo0 bge0.
WARNING: attempt to net_add_domain(netgraph) after domainfinalize()
ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled
<118>Flushed all rules.
<118>00100 allow ip from any to any via lo0
<118>00200 deny ip from any to 127.0.0.0/8
<118>00300 deny ip from 127.0.0.0/8 to any
<118>Firewall rules loaded.
<118>Waiting 30s for an interface to come up: (bge0)
<118>Removing stale Samba tdb files:  done
---Type <return> to continue, or q <return> to quit---
<118>Dec 13 22:34:45 acer bthidd[1083]: syntax error in line 1
<118>Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
<118>ATAidle: configuring device /dev/ad4
<118>Model:			TOSHIBA MK1646GSX                       
<118>Serial:			48AMC6DOT
<118>Firmware Rev:		LB114C  
<118>ATA revision:		ATA-8
<118>LBA 48:			yes
<118>Geometry:		16383 cyls, 16 heads, 63 spt
<118>Capacity:		149GB
<118>SMART Supported: 	yes
<118>SMART Enabled: 		yes
<118>APM Supported: 		yes
<118>APM Enabled: 		yes
<118>AAM Supported: 		no
<118>AAM Enabled: 		no
<118>APM Value: 		128
<118>lircd: WARNING: config file contains no valid remote control definition
<118>Starting hald.
<118>Starting avahi-daemon.
<118>Starting avahi-dnsconfd.
<118>Configuring syscons: keymap keyrate scrnmap font8x16 font8x14 font8x8 blanktime.
<118>Local package initialization:[: =: unexpected operator
<118>00001 allow ip from any to any
<118> rtc.
<118>/etc/rc.d/sysctl: WARNING: sysctl dev.pcm.0.vchans does not exist.
<118>
<118>Sat Dec 13 22:34:49 MSK 2008
<118>date: : Dec 13 22:34:50 acer hald[1400]: 22:34:50.461 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0
<118>Dec 13 22:34:50 acer hald[1400]: 22:34:50.462 [E] ck-tracker.c:792: Could not get seats and sessions
<118>Dec 13 22:34:51 acer hald[1400]: 22:34:51.031 [E] hald_runner.c:671: Error running 'hald-addon-acpi': org.freedesktop.HalRunner.Failed: Start request failed
<118>Dec 13 22:34:51 acer hald[1400]: 22:34:51.031 [E] hald.c:124: Cannot start addon hald-addon-acpi for udi /org/freedesktop/Hal/devices/computer
drm0: <ATI Radeon RS690 X1270 IGP> on vgapci0
vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] Initialized radeon 1.29.0 20080613
info: [drm] Setting GART location based on new memory map
info: [drm] Loading RS690/RS740 Microcode
info: [drm] Num pipes: 1
info: [drm] writeback test succeeded in 1 usecs
drm0: [ITHREAD]
info: [drm] Num pipes: 1
<118>Dec 13 22:35:08 acer login: ROOT LOGIN (root) ON ttyv1
bge0: PHY write timed out (phy 1, reg 0, val 32768)
bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff)
bge0: PHY read timed out (phy 1, reg 24, val 0xffffffff)
bge0: PHY read timed out (phy 1, reg 16, val 0xffffffff)
bge0: PHY write timed out (phy 1, reg 16, val 0)
---Type <return> to continue, or q <return> to quit---
bge0: PHY write timed out (phy 1, reg 23, val 18)
bge0: RX CPU self-diagnostics failed!
bge0: flow-through queue init failed
bge0: initialization failure
ata3: port not implemented
ata4: port not implemented
ata5: port not implemented
ubt_isoc_in_complete2: ubt0 - Isoc-in xfer failed, IOERROR (13). No new xfer will be submitted!
ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted!
ums0: at uhub1 port 1 (addr 2) disconnected
ubt0: at uhub0 port 2 (addr 2) disconnected


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address	= 0x50
fault code		= supervisor read data, page not present
instruction pointer	= 0x8:0xffffffff80551631
stack pointer	        = 0x10:0xfffffffe4005bad0
frame pointer	        = 0x10:0xfffffffe4005bb20
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (thread taskq)
trap number		= 12
panic: page fault
cpuid = 0
Uptime: 58s
Physical memory: 1905 MB
Dumping 206 MB: 191 175 159 143 127 111 95 79 63 47 31 15powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
info: [drm] Num pipes: 1
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
info: [drm] Loading RS690/RS740 Microcode
info: [drm] Num pipes: 1
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow1: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
info: [drm] Num pipes: 1
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
info: [drm] Setting GART location based on new memory map
info: [drm] Loading RS690/RS740 Microcode
info: [drm] Num pipes: 1
info: [drm] writeback test succeeded in 1 usecs
drm0: [ITHREAD]
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
info: [drm] Num pipes: 1
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>Dec 13 22:33:18 acer shutdown: reboot by root: 
powernow0: set freq failed, err 6
---Type <return> to continue, or q <return> to quit---
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>stty: 
powernow0: set freq failed, err 6
powernow0: set freq failed, err 6
<118>Stopping moused.
<118>Waiting for PIDS: 1330powernow0: set freq failed, err 6
powernow0: set freq fai(kgdb) 
(kgdb) 
(kgdb) quit
HP# ll sdocs/kgdb.txt 

-rw-r--r--  1 root  wheel    78K 16 ÄÅË 12:04 kgdb.txt
HP# mail -s kgdb admin@lissyara.su < kgdb.txt 

HP# 
From victor at bsdes.net  Mon Dec 15 23:19:22 2008
From: victor at bsdes.net (Victor Balada Diaz)
Date: Tue Dec 16 07:50:49 2008
Subject: [ATA] and re(4) stability issues
In-Reply-To: <20081215090207.GN1320@alf.bsdes.net>
References: <20081210085934.GB1320@alf.bsdes.net>
	<20081210102800.GH37837@cdnetworks.co.kr>
	<20081210113225.GD1320@alf.bsdes.net>
	<20081210120719.GK37837@cdnetworks.co.kr>
	<20081211075707.GH1320@alf.bsdes.net>
	<20081211081045.GJ1320@alf.bsdes.net>
	<20081211090056.GH42370@cdnetworks.co.kr>
	<20081211095021.GL1320@alf.bsdes.net>
	<20081212121309.GM1320@alf.bsdes.net>
	<20081215090207.GN1320@alf.bsdes.net>
Message-ID: <20081216071919.GR1320@alf.bsdes.net>

On Mon, Dec 15, 2008 at 10:02:07AM +0100, Victor Balada Diaz wrote:
> Stopped stress testing this morning. After all the weekend testing
> seems the re(4) problems were fixed. No single interface up/down error.
> netstat -i reports no errors and everything is fine. Thanks a lot!
> 
> I'm going to deploy the patches on our production machines.
> 
> I've been able to trigger interrupt storms with ATA code, though.

After deploying it in various machines this night i've found in the
logs messages like this one:

re0: watchdog timeout (missed Tx interrupts) -- recovering

I know you told me this is harmless, so this is just so you
know it's happening.

Regards.

-- 
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros. 
From admin at lissyara.su  Tue Dec 16 08:55:23 2008
From: admin at lissyara.su (Alex Keda)
Date: Tue Dec 16 08:55:39 2008
Subject: Semi-working patch for amd64 suspend/resume
In-Reply-To: <4945EB56.1060608@yandex.ru>
References: <1224616985.00027652.1224606603@10.7.7.3>
	<1224728582.00028075.1224715806@10.7.7.3>
	<4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su>
	<494420C4.80702@lissyara.su> <49442375.4010401@root.org>
	<4945EB56.1060608@yandex.ru>
Message-ID: <4947DD70.9040800@lissyara.su>

Andrey V. Elsukov ?????:
> Nate Lawson wrote:
>>> #7  0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at
>>> bus_if.h:46
>>> #8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not
>>> available.
>>> ) at /usr/src/sys/kern/subr_bus.c:2953
>>> #9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at
>>> /usr/src/sys/dev/ata/ata-all.c:713
>>> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context"
>>> is not available.
>>> ) at /usr/src/sys/dev/ata/ata-sata.c:69
>>> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at
>>> /usr/src/sys/kern/subr_taskqueue.c:282
>>> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is
>>> not available.
>>
>> ATA should be disabling its SATA PHY task during suspend, then
>> re-enabling it after resume. Looks like it doesn't do this.
> 
> It seems that resuming of ATA controller is already done.
> AHCI interrupts are enabled and PHY state was changed.
> And task are doing attach of hot-plugged device..
> So, Alex, can you show output of a kgdb command:
> (kgdb) p "%s", msgbufp->msg_ptr
> 
boot verbose, as requested

-------------- next part --------------
Script started on Tue Dec 16 19:49:33 2008
HP# kgdb -q /boot/kernel/kernel vmcore.911

Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/snd_hda.ko
Reading symbols from /boot/kernel/umodem.ko...Reading symbols from /boot/kernel/umodem.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/umodem.ko
Reading symbols from /boot/kernel/acpi_video.ko...Reading symbols from /boot/kernel/acpi_video.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_video.ko
Reading symbols from /boot/kernel/atapicam.ko...Reading symbols from /boot/kernel/atapicam.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/atapicam.ko
Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols from /boot/kernel/acpi_aiboost.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_aiboost.ko
Reading symbols from /boot/kernel/acpi_dock.ko...Reading symbols from /boot/kernel/acpi_dock.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_dock.ko
Reading symbols from /boot/kernel/ng_bt3c.ko...Reading symbols from /boot/kernel/ng_bt3c.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_bt3c.ko
Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/netgraph.ko
Reading symbols from /boot/kernel/ng_btsocket.ko...Reading symbols from /boot/kernel/ng_btsocket.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_btsocket.ko
Reading symbols from /boot/kernel/ng_bluetooth.ko...Reading symbols from /boot/kernel/ng_bluetooth.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_bluetooth.ko
Reading symbols from /boot/kernel/ng_ubt.ko...Reading symbols from /boot/kernel/ng_ubt.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_ubt.ko
Reading symbols from /boot/kernel/ubtbcmfw.ko...Reading symbols from /boot/kernel/ubtbcmfw.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ubtbcmfw.ko
Reading symbols from /boot/kernel/ng_l2cap.ko...Reading symbols from /boot/kernel/ng_l2cap.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ng_l2cap.ko
Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from /boot/kernel/iicbb.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbb.ko
Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from /boot/kernel/iicbus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbus.ko
Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /boot/kernel/tmpfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/tmpfs.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
#0  doadump () at pcpu.h:196
196	pcpu.h: No such file or directory.
	in pcpu.h
(kgdb) bt
#0  doadump () at pcpu.h:196
#1  0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420
#2  0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576
#3  0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/trap.c:759
#4  0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675
#5  0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444
#6  0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217
#7  0xffffffff80551631 in device_attach (dev=0xffffff0001afe900) at bus_if.h:46
#8  0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available.
) at /usr/src/sys/kern/subr_bus.c:2953
#9  0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713
#10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available.
) at /usr/src/sys/dev/ata/ata-sata.c:69
#11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282
#12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available.
) at /usr/src/sys/kern/subr_taskqueue.c:403
#13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 <taskqueue_thread_loop>, arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90)
    at /usr/src/sys/kern/kern_fork.c:821
#14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521
#15 0x0000000000000000 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x0000000000000000 in ?? ()
#18 0x0000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()
#20 0x0000000000000000 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000000 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000e8a000 in ?? ()
#40 0xffffff0001345720 in ?? ()
---Type <return> to continue, or q <return> to quit---
#41 0xffffffff80b50500 in tdq_cpu ()
#42 0xffffffff80b4f880 in affinity ()
#43 0xffffff0001345720 in ?? ()
#44 0xfffffffe4005b690 in ?? ()
#45 0xfffffffe4005b648 in ?? ()
#46 0xffffff0001891ab0 in ?? ()
#47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available.
) at /usr/src/sys/kern/sched_ule.c:1848
Previous frame inner to this frame (corrupt stack?)
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) printf "%s", msgbufp->msg_ptr
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-CURRENT #0: Sat Dec 13 22:29:48 MSK 2008
    lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console
Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80e5f000.
Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff80e5f1f8.
Preloaded elf obj module "/boot/kernel/snd_hda.ko" at 0xffffffff80e5f860.
Preloaded elf obj module "/boot/kernel/umodem.ko" at 0xffffffff80e5fe48.
Preloaded elf obj module "/boot/kernel/acpi_video.ko" at 0xffffffff80e60370.
Preloaded /boot/zfs/zpool.cache "/boot/zfs/zpool.cache" at 0xffffffff80e608e0.
Preloaded elf obj module "/boot/kernel/atapicam.ko" at 0xffffffff80e60940.
Preloaded elf obj module "/boot/kernel/acpi_aiboost.ko" at 0xffffffff80e60f30.
Preloaded elf obj module "/boot/kernel/acpi_dock.ko" at 0xffffffff80e614a0.
Preloaded elf obj module "/boot/kernel/ng_bt3c.ko" at 0xffffffff80e61a10.
Preloaded elf obj module "/boot/kernel/netgraph.ko" at 0xffffffff80e61ff8.
Preloaded elf obj module "/boot/kernel/ng_btsocket.ko" at 0xffffffff80e62668.
Preloaded elf obj module "/boot/kernel/ng_bluetooth.ko" at 0xffffffff80e62cd8.
Preloaded elf obj module "/boot/kernel/ng_ubt.ko" at 0xffffffff80e63248.
Preloaded elf obj module "/boot/kernel/ubtbcmfw.ko" at 0xffffffff80e637b0.
Preloaded elf obj module "/boot/kernel/ng_l2cap.ko" at 0xffffffff80e63ca0.
Preloaded elf obj module "/boot/kernel/iicbb.ko" at 0xffffffff80e64290.
Preloaded elf obj module "/boot/kernel/iicbus.ko" at 0xffffffff80e64738.
Preloaded elf obj module "/boot/kernel/tmpfs.ko" at 0xffffffff80e64ba0.
Timecounter "i8254" frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 1994924370 Hz
CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1994.92-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x60f82  Stepping = 2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x2001<SSE3,CX16>
  AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
  AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
  Cores per package: 2
L1 2MB data TLB: 8 entries, fully associative
L1 2MB instruction TLB: 8 entries, fully associative
L1 4KB data TLB: 32 entries, fully associative
L1 4KB instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 2MB unified TLB: 0 entries, disabled/not present
L2 4KB data TLB: 512 entries, 4-way associative
---Type <return> to continue, or q <return> to quit---
L2 4KB instruction TLB: 512 entries, 4-way associative
L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative
usable memory = 1998295040 (1905 MB)
Physical memory chunk(s):
0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages)
0x0000000000e92000 - 0x0000000074ad3fff, 1942233088 bytes (474178 pages)
avail memory  = 1929797632 (1840 MB)
ACPI APIC Table: <HP     0944    >
INTR: Adding local APIC 1 as a target
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 2
ULE: setup cpu 0
ULE: setup cpu 1
ACPI: RSDP @ 0x0xfe0b0/0x0024 (v  2 HP    )
ACPI: XSDT @ 0x0x77fc81bc/0x0064 (v  1 HPQOEM SLIC-MPC 0x00000001 HP   0x00000001)
ACPI: FACP @ 0x0x77fc8084/0x00F4 (v  4 HP     0944     0x00000003 HP   0x00000001)
ACPI Error (tbfadt-0516): 32/64X address mismatch in "Pm2ControlBlock": [    8800] [       0    8100], using 64X [20070320]
ACPI: DSDT @ 0x0x77fc84a4/0x1193C (v  1 HP        SB400 0x00010000 MSFT 0x03000001)
ACPI: FACS @ 0x0x77fe7d80/0x0040
ACPI: SLIC @ 0x0x77fc8220/0x0176 (v  1 HPQOEM SLIC-MPC 0x00000001 HP   0x00000001)
ACPI: EPTH @ 0x0x77fc8398/0x0038 (v  1 HP     0944     0x00000001 HP   0x00000001)
ACPI: APIC @ 0x0x77fc83d0/0x0062 (v  1 HP     0944     0x00000001 HP   0x00000001)
ACPI: MCFG @ 0x0x77fc8434/0x003C (v  1 HP     0944     0x00000001 HP   0x00000001)
ACPI: TCPA @ 0x0x77fc8470/0x0032 (v  2 HP     0944     0x00000001 HP   0x00000001)
ACPI: SSDT @ 0x0x77fd9de0/0x0059 (v  1 HP       HPQNLP 0x00000001 MSFT 0x03000001)
ACPI: SSDT @ 0x0x77fd9e39/0x0206 (v  1 HP     PSSTBLID 0x00000001 HP   0x00000001)
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000
ioapic0: Changing APIC ID to 2
ioapic0: Routing external 8259A's -> intpin 0
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
MADT: Interrupt override: source 9, irq 9
ioapic0: intpin 9 trigger: level
ioapic0: intpin 9 polarity: low
lapic0: Routing NMI -> LINT1
lapic0: LINT1 trigger: edge
lapic0: LINT1 polarity: high
ioapic0 <Version 2.1> irqs 0-23 on motherboard
cpu0 BSP:
---Type <return> to continue, or q <return> to quit---
     ID: 0x00000000   VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
  lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
  timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00000400
ath_rate: version 1.9 <SampleRate bit-rate selection algorithm>
wlan: <802.11 Link Layer>
snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024]
feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_buffersize=16384 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25
null: <null device, zero device>
random: <entropy source, Software, Yarrow>
nfslock: pseudo-device
io: <I/O>
kbd: new array size 4
kbd1 at kbdmux0
mem: <memory>
hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Dec 13 2008 22:26:24)
acpi0: <HPQOEM SLIC-MPC> on motherboard
PCIe: Memory Mapped configuration base @ 0xe0000000
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C08C.C08D.C154 -> bus 1 dev 5 func 0
ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48
acpi0: [MPSAFE]
acpi0: [ITHREAD]
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C093 -> bus 0 dev 0 func 0
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C090 -> bus 0 dev 0 func 0
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C09F.C0B2 -> bus 0 dev 20 func 0
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C275.C278 -> bus 0 dev 18 func 0
acpi0: Power Button (fixed)
acpi0: wakeup code va 0xfffffffe40004000 pa 0x4000
acpi_bus_number: root bus has no _BBN, assuming 0
AcpiOsDerivePciId: \_SB_.C08B.C096 -> bus 0 dev 0 func 0
unknown: I/O range not supported
acpi0: reservation of 0, 8000000 (3) failed
acpi0: reservation of 100000, fff00000 (3) failed
ACPI timer: 1/1 1/1 1/1 1/1 1/1 0/3 1/1 1/1 1/1 1/1 -> 9
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x11> port 0x62,0x66 on acpi0
pci_link0:        Index  IRQ  Rtd  Ref  IRQs
---Type <return> to continue, or q <return> to quit---
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link1:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link2:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link3:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link4:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link5:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  9
  Validation          0  255   N     0  9
  After Disable       0  255   N     0  9
pci_link6:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pci_link7:        Index  IRQ  Rtd  Ref  IRQs
  Initial Probe       0  255   N     0  10 11
  Validation          0  255   N     0  10 11
  After Disable       0  255   N     0  10 11
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: domain=0, physical bus=0
found->	vendor=0x1002, dev=0x7910, revid=0x00
	domain=0, bus=0, slot=0, func=0
	class=06-00-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x2220, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x7912, revid=0x00
	domain=0, bus=0, slot=1, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
---Type <return> to continue, or q <return> to quit---
	cmdreg=0x0007, statreg=0x0230, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x7914, revid=0x00
	domain=0, bus=0, slot=4, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
	cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
	powerspec 3  supports D0 D3  current D0
	MSI supports 1 message
found->	vendor=0x1002, dev=0x7915, revid=0x00
	domain=0, bus=0, slot=5, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
	cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
	powerspec 3  supports D0 D3  current D0
	MSI supports 1 message
found->	vendor=0x1002, dev=0x7916, revid=0x00
	domain=0, bus=0, slot=6, func=0
	class=06-04-00, hdrtype=0x01, mfdev=0
	cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
	powerspec 3  supports D0 D3  current D0
	MSI supports 1 message
found->	vendor=0x1002, dev=0x4380, revid=0x00
	domain=0, bus=0, slot=18, func=0
	class=01-01-8f, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x0230, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 2  supports D0 D3  current D0
	map[10]: type I/O Port, range 32, base 0x9000, size  3, enabled
	map[14]: type I/O Port, range 32, base 0x9008, size  2, enabled
	map[18]: type I/O Port, range 32, base 0x9010, size  3, enabled
	map[1c]: type I/O Port, range 32, base 0x5018, size  2, enabled
	map[20]: type I/O Port, range 32, base 0x5020, size  4, enabled
	map[24]: type Memory, range 32, base 0xd0409000, size 10, enabled
pcib0: matched entry for 0.18.INTA
pcib0: slot 18 INTA hardwired to IRQ 16
found->	vendor=0x1002, dev=0x4387, revid=0x00
	domain=0, bus=0, slot=19, func=0
	class=0c-03-10, hdrtype=0x00, mfdev=1
	cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords)
---Type <return> to continue, or q <return> to quit---
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=11
	map[10]: type Memory, range 32, base 0xd0401000, size 12, enabled
pcib0: matched entry for 0.19.INTA
pcib0: slot 19 INTA hardwired to IRQ 23
found->	vendor=0x1002, dev=0x4388, revid=0x00
	domain=0, bus=0, slot=19, func=1
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=5
	map[10]: type Memory, range 32, base 0xd0402000, size 12, enabled
pcib0: matched entry for 0.19.INTB
pcib0: slot 19 INTB hardwired to IRQ 17
found->	vendor=0x1002, dev=0x4389, revid=0x00
	domain=0, bus=0, slot=19, func=2
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=c, irq=5
	map[10]: type Memory, range 32, base 0xd0403000, size 12, enabled
pcib0: matched entry for 0.19.INTC
pcib0: slot 19 INTC hardwired to IRQ 17
found->	vendor=0x1002, dev=0x438a, revid=0x00
	domain=0, bus=0, slot=19, func=3
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=5
	map[10]: type Memory, range 32, base 0xd0404000, size 12, enabled
pcib0: matched entry for 0.19.INTB
pcib0: slot 19 INTB hardwired to IRQ 17
found->	vendor=0x1002, dev=0x438b, revid=0x00
	domain=0, bus=0, slot=19, func=4
	class=0c-03-10, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=c, irq=5
	map[10]: type Memory, range 32, base 0xd0405000, size 12, enabled
pcib0: matched entry for 0.19.INTC
pcib0: slot 19 INTC hardwired to IRQ 17
found->	vendor=0x1002, dev=0x4386, revid=0x00
---Type <return> to continue, or q <return> to quit---
	domain=0, bus=0, slot=19, func=5
	class=0c-03-20, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=d, irq=11
	powerspec 2  supports D0 D1 D2 D3  current D0
	map[10]: type Memory, range 32, base 0xd0406000, size  8, enabled
pcib0: matched entry for 0.19.INTD
pcib0: slot 19 INTD hardwired to IRQ 23
found->	vendor=0x1002, dev=0x4385, revid=0x14
	domain=0, bus=0, slot=20, func=0
	class=0c-05-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0003, statreg=0x0230, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	map[10]: type I/O Port, range 32, base 0x8200, size  4, enabled
found->	vendor=0x1002, dev=0x438c, revid=0x00
	domain=0, bus=0, slot=20, func=1
	class=01-01-82, hdrtype=0x00, mfdev=0
	cmdreg=0x0005, statreg=0x0220, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	map[20]: type I/O Port, range 32, base 0x5040, size  4, enabled
pcib0: matched entry for 0.20.INTA
pcib0: slot 20 INTA hardwired to IRQ 16
found->	vendor=0x1002, dev=0x4383, revid=0x00
	domain=0, bus=0, slot=20, func=2
	class=04-03-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x0410, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 2  supports D0 D3  current D0
	map[10]: type Memory, range 64, base 0xd0408000, size 14, enabled
pcib0: matched entry for 0.20.INTA
pcib0: slot 20 INTA hardwired to IRQ 16
found->	vendor=0x1002, dev=0x438d, revid=0x00
	domain=0, bus=0, slot=20, func=3
	class=06-01-00, hdrtype=0x00, mfdev=1
	cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1002, dev=0x4384, revid=0x00
	domain=0, bus=0, slot=20, func=4
	class=06-04-01, hdrtype=0x01, mfdev=1
---Type <return> to continue, or q <return> to quit---
	cmdreg=0x0027, statreg=0x02a0, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1100, revid=0x00
	domain=0, bus=0, slot=24, func=0
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1101, revid=0x00
	domain=0, bus=0, slot=24, func=1
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1102, revid=0x00
	domain=0, bus=0, slot=24, func=2
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found->	vendor=0x1022, dev=0x1103, revid=0x00
	domain=0, bus=0, slot=24, func=3
	class=06-00-00, hdrtype=0x00, mfdev=1
	cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pcib1:   domain            0
pcib1:   secondary bus     1
pcib1:   subordinate bus   1
pcib1:   I/O decode        0x4000-0x4fff
pcib1:   memory decode     0xd0200000-0xd03fffff
pcib1:   prefetched decode 0xc0000000-0xc7ffffff
pci1: <ACPI PCI bus> on pcib1
pci1: domain=0, physical bus=1
found->	vendor=0x1002, dev=0x791f, revid=0x00
	domain=0, bus=1, slot=5, func=0
	class=03-00-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=b, irq=11
	powerspec 2  supports D0 D1 D2 D3  current D0
	MSI supports 1 message, 64 bit
	map[10]: type Prefetchable Memory, range 64, base 0xc0000000, size 27, enabled
pcib1: requested memory range 0xc0000000-0xc7ffffff: good
	map[18]: type Memory, range 64, base 0xd0200000, size 16, enabled
---Type <return> to continue, or q <return> to quit---
pcib1: requested memory range 0xd0200000-0xd020ffff: good
	map[20]: type I/O Port, range 32, base 0x4000, size  8, enabled
pcib1: requested I/O range 0x4000-0x40ff: in range
	map[24]: type Memory, range 32, base 0xd0300000, size 20, enabled
pcib1: requested memory range 0xd0300000-0xd03fffff: good
pcib1: matched entry for 1.5.INTB
pcib1: slot 5 INTB hardwired to IRQ 19
vgapci0: <VGA-compatible display> port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1
acpi_video0: <ACPI video extension> on vgapci0
found Internal/Integrated Digital Flat Panel(110), idx#0, port#1, detectable by BIOS, head #0
found VGA CRT or VESA Compatible Analog Monitor(100), idx#0, port#0, detectable by BIOS, head #0
found TV/HDTV or Analog-Video Monitor(200), idx#0, port#0, detectable by BIOS, head #0
found TV/HDTV or Analog-Video Monitor(210), idx#0, port#1, detectable by BIOS, head #0
pcib2: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pcib2:   domain            0
pcib2:   secondary bus     16
pcib2:   subordinate bus   16
pcib2:   I/O decode        0xf000-0xfff
pcib2:   memory decode     0xd0000000-0xd00fffff
pcib2:   no prefetched decode
pcib2: could not get PCI interrupt routing table for \_SB_.C08B.C250 - AE_NOT_FOUND
pci16: <ACPI PCI bus> on pcib2
pci16: domain=0, physical bus=16
found->	vendor=0x14e4, dev=0x1713, revid=0x02
	domain=0, bus=16, slot=0, func=0
	class=02-00-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 3  supports D0 D3  current D0
	MSI supports 1 message, 64 bit
	map[10]: type Memory, range 64, base 0xd0000000, size 16, enabled
pcib2: requested memory range 0xd0000000-0xd000ffff: good
pcib0: matched entry for 0.4.INTA
pcib0: slot 4 INTA hardwired to IRQ 16
pcib2: slot 0 INTA is routed to irq 16
bge0: <Broadcom BCM5906 A2, ASIC rev. 0xc002> mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16
bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd0000000
bge0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 256 to vector 49
bge0: using IRQ 256 for MSI
miibus0: <MII bus> on bge0
---Type <return> to continue, or q <return> to quit---
brgphy0: <BCM5906 10/100baseTX PHY> PHY 1 on miibus0
brgphy0: OUI 0x000af7, model 0x0004, rev. 0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bge0: bpf attached
bge0: Ethernet address: 00:1f:29:89:38:f3
bge0: [MPSAFE]
bge0: [ITHREAD]
pcib3: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pcib3:   domain            0
pcib3:   secondary bus     32
pcib3:   subordinate bus   32
pcib3:   I/O decode        0x2000-0x3fff
pcib3:   memory decode     0xcc000000-0xcfffffff
pcib3:   no prefetched decode
pcib3: could not get PCI interrupt routing table for \_SB_.C08B.C255 - AE_NOT_FOUND
pci32: <ACPI PCI bus> on pcib3
pci32: domain=0, physical bus=32
pcib4: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pcib4:   domain            0
pcib4:   secondary bus     48
pcib4:   subordinate bus   48
pcib4:   I/O decode        0xf000-0xfff
pcib4:   memory decode     0xc8000000-0xc80fffff
pcib4:   no prefetched decode
pcib4: could not get PCI interrupt routing table for \_SB_.C08B.C25F - AE_NOT_FOUND
pci48: <ACPI PCI bus> on pcib4
pci48: domain=0, physical bus=48
found->	vendor=0x14e4, dev=0x4312, revid=0x02
	domain=0, bus=48, slot=0, func=0
	class=02-80-00, hdrtype=0x00, mfdev=0
	cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords)
	lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
	intpin=a, irq=10
	powerspec 3  supports D0 D1 D2 D3  current D0
	MSI supports 1 message, 64 bit
	map[10]: type Memory, range 64, base 0xc8000000, size 14, enabled
pcib4: requested memory range 0xc8000000-0xc8003fff: good
pcib0: matched entry for 0.6.INTA
pcib0: slot 6 INTA hardwired to IRQ 18
pcib4: slot 0 INTA is routed to irq 18
pci48: <network> at device 0.0 (no driver attached)
atapci0: <ATI IXP600 SATA300 controller> port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at devi---Type <return> to continue, or q <return> to quit---
ce 18.0 on pci0
atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x5020
atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xd0409000
ioapic0: routing intpin 16 (PCI IRQ 16) to vector 50
atapci0: [MPSAFE]
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports PM not supported
ata2: <ATA channel 0> on atapci0
ata2: SATA connect time=0ms
ata2: BUSY wait time=1ms
ata2: SIGNATURE: 00000101
ata2: ahci_reset devices=00000001
ata2: [MPSAFE]
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: port not implemented
ata3: [MPSAFE]
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: port not implemented
ata4: [MPSAFE]
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: port not implemented
ata5: [MPSAFE]
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0
ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0401000
ioapic0: routing intpin 23 (PCI IRQ 23) to vector 51
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0
ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0402000
ioapic0: routing intpin 17 (PCI IRQ 17) to vector 52
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
---Type <return> to continue, or q <return> to quit---
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0
ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0403000
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: <OHCI (generic) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0
ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0404000
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3: <OHCI (generic) USB controller> on ohci3
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ohci4: <OHCI (generic) USB controller> mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0
ohci4: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0405000
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: <OHCI (generic) USB controller> on ohci4
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0
ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xd0406000
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
ehci0: Dropped interrupts workaround enabled
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci0
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 10 ports with 10 removable, self powered
---Type <return> to continue, or q <return> to quit---
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0x5040
ata0: <ATA channel 0> on atapci1
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
ata0: reset tp2 stat0=00 stat1=00 devices=0x10000
ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53
ata0: [MPSAFE]
ata0: [ITHREAD]
hdac0: <ATI SB600 High Definition Audio Controller> irq 16 at device 20.2 on pci0
hdac0: HDA Driver Revision: 20081123_0118
hdac0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000
hdac0: [MPSAFE]
hdac0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib5: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pcib5:   domain            0
pcib5:   secondary bus     2
pcib5:   subordinate bus   3
pcib5:   I/O decode        0xf000-0xfff
pcib5:   memory decode     0xd0100000-0xd01fffff
pcib5:   no prefetched decode
pcib5:   Subtractively decoded bridge.
pci2: <ACPI PCI bus> on pcib5
pci2: domain=0, physical bus=2
found->	vendor=0x1180, dev=0x0476, revid=0xb6
	domain=0, bus=2, slot=4, func=0
	class=06-07-00, hdrtype=0x02, mfdev=1
	cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords)
	lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns)
	intpin=a, irq=10
	powerspec 2  supports D0 D1 D2 D3  current D0
	map[10]: type Memory, range 32, base 0xd0100000, size 12, enabled
pcib5: requested memory range 0xd0100000-0xd0100fff: good
pcib5: matched entry for 2.4.INTA
pcib5: slot 4 INTA hardwired to IRQ 20
cbb0: <RF5C476 PCI-CardBus Bridge> mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2
---Type <return> to continue, or q <return> to quit---
cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0100000
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
ioapic0: routing intpin 20 (PCI IRQ 20) to vector 54
cbb0: [MPSAFE]
cbb0: [FILTER]
cbb0: PCI Configuration space:
  0x00: 0x04761180 0x02100007 0x060700b6 0x00824000 
  0x10: 0xd0100000 0x020000dc 0x20030302 0xfffff000 
  0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 
  0x30: 0x00000000 0xfffffffc 0x00000000 0x07000114 
  0x40: 0x30c2103c 0x00000001 0x00000000 0x00000000 
  0x50: 0x00000000 0x00000000 0x00000000 0x00000000 
  0x60: 0x00000000 0x00000000 0x00000000 0x00000000 
  0x70: 0x00000000 0x00000000 0x00000000 0x00000000 
  0x80: 0x30a00001 0x00000000 0x04630463 0x00000000 
  0x90: 0x00000000 0x00000000 0x00000000 0x00000000 
  0xa0: 0x00000008 0x00000000 0x00000000 0x00000000 
  0xb0: 0x00000000 0xbe000000 0x00003000 0x00000000 
  0xc0: 0x30c2103c 0x00000000 0x00000000 0x00000000 
  0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 
  0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 
  0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 
battery0: <ACPI Control Method Battery> on acpi0
battery1: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
acpi_button0: <Sleep Button> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71,0x72-0x73 irq 8 on acpi0
atrtc0: registered as a time-of-day clock (resolution 1000000us)
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0065
atkbd: keyboard ID 0x41ab (2)
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
ioapic0: routing intpin 1 (ISA IRQ 1) to vector 55
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: unable to allocate IRQ
psmcpnp0: <PS/2 mouse port> irq 12 on acpi0
---Type <return> to continue, or q <return> to quit---
psm0: current command byte:0065
psm0: <PS/2 Mouse> irq 12 on atkbdc0
ioapic0: routing intpin 12 (ISA IRQ 12) to vector 56
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3-00, 3 buttons
psm0: config:00000000, flags:00000008, packet size:4
psm0: syncmask:08, syncbits:00
cpu0: <ACPI CPU> on acpi0
cpu0: switching to generic Cx mode
acpi_throttle0: <ACPI CPU Throttling> on cpu0
acpi_throttle0: P_CNT from P_BLK 0x8010
powernow0: <PowerNow! K8> on cpu0
cpu1: <ACPI CPU> on acpi0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
powernow1: <PowerNow! K8> on cpu1
ahc_isa_probe 0: ioport 0xc00 alloc failed
ex_isa_identify()
isa_probe_children: disabling PnP devices
atkbdc: atkbdc0 already exists; skipping it
sc: sc0 already exists; skipping it
vga: vga0 already exists; skipping it
isa_probe_children: probing non-PnP devices
orm0: <ISA Option ROM> at iomem 0xd0000-0xd0fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sc0: fb0, kbd1, terminal emulator: sc (syscons terminal)
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
ppc0: cannot reserve I/O port range
ppc0: <Parallel port> failed to probe at irq 7 on isa0
uart0: <ns8250> failed to probe at port 0x3f8-0x3ff irq 4 on isa0
uart1: <ns8250> failed to probe at port 0x2f8-0x2ff irq 3 on isa0
uart2: not probed (disabled)
uart3: not probed (disabled)
isa_probe_children: probing PnP devices
ubt0: <Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.00, addr 2> on uhub0
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=10, buffer size=640
ums0: <Logitech Optical USB Mouse, class 0/0, rev 2.00/3.40, addr 2> on uhub1
---Type <return> to continue, or q <return> to quit---
ums0: 3 buttons and Z dir.
Device configuration finished.
Reducing kern.maxvnodes 124747 -> 100000
procfs registered
lapic: Divisor 2, Frequency 99746224 hz
Timecounter "TSC" frequency 1994924370 Hz quality -100
Timecounters tick every 1.000 msec
lo0: bpf attached
hptrr: no controller detected.
ata0: identify ch->devices=00010000
acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0
acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0
acpi_tz0: _AC1: temperature 66.0 >= setpoint 60.0
acpi_tz0: switched from NONE to _AC1: 66.0C
ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire
battery0: battery initialization start
acd0: setting PIO4 on IXP600 chip
battery1: battery initialization start
acpi_acad0: acline initialization start
acd0: <HL-DT-ST DVDRAM GSA-T20L/NC08> DVDR drive at ata0 as master
acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 2048KB buffer, PIO4
acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet
acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray, unlocked
acd0: Medium: no/blank disc
ata2: identify ch->devices=00000001
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire
ad4: 152627MB <TOSHIBA MK1646GSX LB114C> at ata2-master SATA300
ad4: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue
acpi_acad0: On Line
acpi_acad0: acline initialization done, tried 1 times
acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0
acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0
acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0
acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0
battery0: battery initialization done, tried 1 times
GEOM: new disk ad4
ad4: Silicon Image check3 failed
ad4: Adaptec check1 failed
ad4: LSI (v3) check1 failed
ad4: LSI (v2) check1 failed
---Type <return> to continue, or q <return> to quit---
ad4: FreeBSD check1 failed
ata3: identify ch->devices=00000000
ata4: identify ch->devices=00000000
ata5: identify ch->devices=00000000
hdac0: Probing codec #0...
hdac0: HDA Codec #0: Analog Devices AD1981HD
hdac0:  HDA Codec ID: 0x11d41981
hdac0:        Vendor: 0x11d4
hdac0:        Device: 0x1981
hdac0:      Revision: 0x02
hdac0:      Stepping: 0x00
hdac0: PCI Subvendor: 0x30c2103c
hdac0: 	Found audio FG nid=1 startnode=2 endnode=32 total=30
hdac0: Probing codec #1...
hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown)
hdac0:  HDA Codec ID: 0x11c11040
hdac0:        Vendor: 0x11c1
hdac0:        Device: 0x1040
hdac0:      Revision: 0x02
hdac0:      Stepping: 0x00
hdac0: PCI Subvendor: 0x30c2103c
hdac0: 	Found modem FG nid=1 startnode=2 endnode=127 total=125
hdac0: 
hdac0: Processing audio FG cad=0 nid=1...
hdac0: GPIO: 0x40000004 NumGPIO=4 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1
hdac0: GHOST: nid=2 j=0 entnum=4 index=0 res=0x00000401
hdac0:  nid 5 0x92174110 as  1 seq  0       Speaker Fixed jack  7 loc 18 color   Green misc 1
hdac0:  nid 6 0x0421201f as  1 seq 15    Headphones  Jack jack  1 loc  4 color    Grey misc 0
hdac0:  nid 7 0x410710f0 as 15 seq  0      Line-out  None jack  7 loc  1 color   Black misc 0
hdac0:  nid 8 0x04a12020 as  2 seq  0           Mic  Jack jack  1 loc  4 color    Grey misc 0
hdac0:  nid 9 0x0181302e as  2 seq 14       Line-in  Jack jack  1 loc  1 color    Blue misc 0
hdac0:  nid 10 0x4145f0f0 as 15 seq  0     SPDIF-out  None jack  5 loc  1 color   Other misc 0
hdac0:  nid 22 0x995711f0 as 15 seq  0   Digital-out Fixed jack  7 loc 25 color   Black misc 1
hdac0:  nid 23 0x5993e0f0 as 15 seq  0           AUX  None jack  3 loc 25 color   White misc 0
hdac0:  nid 24 0xf0a79159 as  5 seq  9           Mic  Both jack  7 loc 48 color    Pink misc 1
hdac0:  nid 25 0x593310f0 as 15 seq  0            CD  None jack  3 loc 25 color   Black misc 0
hdac0: Patched pins configuration:
hdac0:  nid 5 0x92174110 as  1 seq  0       Speaker Fixed jack  7 loc 18 color   Green misc 1
hdac0:  nid 6 0x0421201f as  1 seq 15    Headphones  Jack jack  1 loc  4 color    Grey misc 0
hdac0:  nid 7 0x410710f0 as 15 seq  0      Line-out  None jack  7 loc  1 color   Black misc 0 [DISABLED]
hdac0:  nid 8 0x04a12020 as  2 seq  0           Mic  Jack jack  1 loc  4 color    Grey misc 0
hdac0:  nid 9 0x0181302e as  2 seq 14       Line-in  Jack jack  1 loc  1 color    Blue misc 0
---Type <return> to continue, or q <return> to quit---
hdac0:  nid 10 0x4145f0f0 as 15 seq  0     SPDIF-out  None jack  5 loc  1 color   Other misc 0 [DISABLED]
hdac0:  nid 22 0x995711f0 as 15 seq  0   Digital-out Fixed jack  7 loc 25 color   Black misc 1
hdac0:  nid 23 0x5993e0f0 as 15 seq  0           AUX  None jack  3 loc 25 color   White misc 0 [DISABLED]
hdac0:  nid 24 0xf0a79159 as  5 seq  9           Mic  Both jack  7 loc 48 color    Pink misc 1
hdac0:  nid 25 0x593310f0 as 15 seq  0            CD  None jack  3 loc 25 color   Black misc 0 [DISABLED]
hdac0: 4 associations found:
hdac0: Association 0 (1) out:
hdac0:  Pin nid=5 seq=0
hdac0:  Pin nid=6 seq=15
hdac0: Association 1 (2) in:
hdac0:  Pin nid=8 seq=0
hdac0:  Pin nid=9 seq=14
hdac0: Association 2 (5) in:
hdac0:  Pin nid=24 seq=9
hdac0: Association 3 (15) out:
hdac0:  Pin nid=22 seq=0
hdac0: Tracing association 0 (1)
hdac0:  Pin 5 traced to DAC 3
hdac0:  Pin 6 traced to DAC 3 and hpredir 0
hdac0: Association 0 (1) trace succeded
hdac0: Tracing association 1 (2)
hdac0:  Pin 8 traced to ADC 4
hdac0:  Pin 9 traced to ADC 4
hdac0: Association 1 (2) trace succeded
hdac0: Tracing association 2 (5)
hdac0: Association 2 (5) trace failed
hdac0: Tracing association 3 (15)
hdac0:  Unable to trace pin 22 seq 0 with min nid 0
hdac0: Association 3 (15) trace failed
hdac0: Tracing input monitor
hdac0:  Tracing nid 12 to out
hdac0: Tracing beeper
hdac0: Enabling headphone/speaker audio routing switching:
hdac0: 	as=0 sense nid=6 [UNSOL]
hdac0: Pin sense: nid=6 res=0x0000f5df
hdac0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref
hdac0: 
hdac0: +-------------------+
hdac0: | DUMPING HDA NODES |
hdac0: +-------------------+
hdac0: 
hdac0: Default Parameter
---Type <return> to continue, or q <return> to quit---
hdac0: -----------------
hdac0:      Stream cap: 0x00000001
hdac0:                  PCM
hdac0:         PCM cap: 0x000e007f
hdac0:                  16 20 24 bits, 8 11 16 22 32 44 48 KHz
hdac0:          IN amp: 0x00270300
hdac0:         OUT amp: 0x80053f3d
hdac0: 
hdac0:             nid: 2 [DISABLED]
hdac0:            Name: audio output
hdac0:      Widget cap: 0x00030311
hdac0:                  DIGITAL STEREO
hdac0:      Stream cap: 0x00000005
hdac0:                  AC3 PCM
hdac0:         PCM cap: 0x00020060
hdac0:                  16 bits, 44 48 KHz
hdac0:     connections: 2
hdac0:           |
hdac0:           + [DISABLED] <- nid=1 [GHOST!] [UNKNOWN] (selected)
hdac0:           + <- nid=4 [audio input]
hdac0: 
hdac0:             nid: 3
hdac0:            Name: audio output
hdac0:      Widget cap: 0x00000441
hdac0:                  PWR PROC STEREO
hdac0:     Association: 0 (0x00008001)
hdac0:             OSS: pcm (pcm)
hdac0:      Stream cap: 0x00000001
hdac0:                  PCM
hdac0:         PCM cap: 0x000e007f
hdac0:                  16 20 24 bits, 8 11 16 22 32 44 48 KHz
hdac0: 
hdac0:             nid: 4
hdac0:            Name: audio input
hdac0:      Widget cap: 0x00100511
hdac0:                  PWR STEREO
hdac0:     Association: 1 (0x00004001)
hdac0:      Stream cap: 0x00000001
hdac0:                  PCM
hdac0:         PCM cap: 0x0006007f
hdac0:                  16 20 bits, 8 11 16 22 32 44 48 KHz
hdac0:     connections: 1
---Type <return> to continue, or q <return> to quit---
hdac0:           |
hdac0:           + <- nid=21 [audio selector]
hdac0: 
hdac0:             nid: 5
hdac0:            Name: pin: Speaker (Fixed)
hdac0:      Widget cap: 0x00400187
hdac0:                  UNSOL STEREO
hdac0:     Association: 0 (0x00000001)
hdac0:         Pin cap: 0x0001173f
hdac0:                  ISC TRQD PDC HP OUT IN VREF[ 50 80 GROUND HIZ ] EAPD
hdac0:      Pin config: 0x92174110
hdac0:     Pin control: 0x00000040 OUT
hdac0:            EAPD: 0x00000002
hdac0:      Output amp: 0x80053f3d
hdac0:                  mute=1 step=63 size=5 offset=61
hdac0:       Input amp: 0x00270300
hdac0:                  mute=0 step=3 size=39 offset=0
hdac0:     connections: 2
hdac0:           |
hdac0:           + <- nid=3 [audio output] (selected)
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0: 
hdac0:             nid: 6
hdac0:            Name: pin: Headphones (Jack)
hdac0:      Widget cap: 0x00400185
hdac0:                  UNSOL STEREO
hdac0:     Association: 0 (0x00008000)
hdac0:         Pin cap: 0x0000001f
hdac0:                  ISC TRQD PDC HP OUT
hdac0:      Pin config: 0x0421201f
hdac0:     Pin control: 0x000000c0 HP OUT
hdac0:      Output amp: 0x80053f3d
hdac0:                  mute=1 step=63 size=5 offset=61
hdac0:     connections: 2
hdac0:           |
hdac0:           + <- nid=3 [audio output] (selected)
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0: 
hdac0:             nid: 7 [DISABLED]
hdac0:            Name: pin: Line-out (None)
hdac0:      Widget cap: 0x00400104
hdac0:         Pin cap: 0x00000010
---Type <return> to continue, or q <return> to quit---
hdac0:                  OUT
hdac0:      Pin config: 0x410710f0
hdac0:     Pin control: 0x00000000
hdac0:      Output amp: 0x80053f3d
hdac0:                  mute=1 step=63 size=5 offset=61
hdac0:     connections: 1
hdac0:           |
hdac0:           + [DISABLED] <- nid=15 [audio mixer] [DISABLED]
hdac0: 
hdac0:             nid: 8
hdac0:            Name: pin: Mic (Jack)
hdac0:      Widget cap: 0x00400083
hdac0:                  UNSOL STEREO
hdac0:     Association: 1 (0x00000001)
hdac0:             OSS: mic (mic)
hdac0:         Pin cap: 0x00001727
hdac0:                  ISC TRQD PDC IN VREF[ 50 80 GROUND HIZ ]
hdac0:      Pin config: 0x04a12020
hdac0:     Pin control: 0x00000024 IN VREFs
hdac0:       Input amp: 0x00270300
hdac0:                  mute=0 step=3 size=39 offset=0
hdac0: 
hdac0:             nid: 9
hdac0:            Name: pin: Line-in (Jack)
hdac0:      Widget cap: 0x00400187
hdac0:                  UNSOL STEREO
hdac0:     Association: 1 (0x00004000)
hdac0:             OSS: line (line)
hdac0:         Pin cap: 0x00001737
hdac0:                  ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ]
hdac0:      Pin config: 0x0181302e
hdac0:     Pin control: 0x00000024 IN VREFs
hdac0:      Output amp: 0x80053f3d
hdac0:                  mute=1 step=63 size=5 offset=61
hdac0:       Input amp: 0x00270300
hdac0:                  mute=0 step=3 size=39 offset=0
hdac0:     connections: 2
hdac0:           |
hdac0:           + [DISABLED] <- nid=3 [audio output] (selected)
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0: 
hdac0:             nid: 10 [DISABLED]
---Type <return> to continue, or q <return> to quit---
hdac0:            Name: pin: SPDIF-out (None)
hdac0:      Widget cap: 0x00400301
hdac0:                  DIGITAL STEREO
hdac0:         Pin cap: 0x00000010
hdac0:                  OUT
hdac0:      Pin config: 0x4145f0f0
hdac0:     Pin control: 0x00000000
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=2 [audio output] [DISABLED]
hdac0: 
hdac0:             nid: 11 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x00300101
hdac0:                  STEREO
hdac0:     connections: 6
hdac0:           |
hdac0:           + <- nid=3 [audio output] (selected)
hdac0:           + <- nid=12 [audio mixer]
hdac0:           + <- nid=9 [pin: Line-in (Jack)]
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0:           + <- nid=5 [pin: Speaker (Fixed)]
hdac0:           + <- nid=24 [pin: Mic (Both)] [DISABLED]
hdac0: 
hdac0:             nid: 12
hdac0:            Name: audio mixer
hdac0:      Widget cap: 0x00200101
hdac0:                  STEREO
hdac0:     Association: 1 (0x00000001)
hdac0:             OSS: mic
hdac0:     connections: 2
hdac0:           |
hdac0:           + <- nid=30 [audio selector]
hdac0:           + [DISABLED] <- nid=31 [audio selector] [DISABLED]
hdac0: 
hdac0:             nid: 13 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010c
hdac0:      Output amp: 0x800b0f0f
hdac0:                  mute=1 step=15 size=11 offset=15
hdac0:     connections: 2
hdac0:           |
---Type <return> to continue, or q <return> to quit---
hdac0:           + <- nid=16 [beep widget] (selected)
hdac0:           + <- nid=22 [pin: Digital-out (Fixed)] [DISABLED]
hdac0: 
hdac0:             nid: 14 [DISABLED]
hdac0:            Name: audio mixer
hdac0:      Widget cap: 0x00200101
hdac0:                  STEREO
hdac0:     connections: 8
hdac0:           |
hdac0:           + <- nid=13 [audio selector] [DISABLED]
hdac0:           + <- nid=17 [audio selector] [DISABLED]
hdac0:           + <- nid=18 [audio selector] [DISABLED]
hdac0:           + <- nid=19 [audio selector] [DISABLED]
hdac0:           + <- nid=26 [audio selector] [DISABLED]
hdac0:           + <- nid=27 [audio selector] [DISABLED]
hdac0:           + <- nid=28 [audio selector] [DISABLED]
hdac0:           + <- nid=29 [audio selector] [DISABLED]
hdac0: 
hdac0:             nid: 15 [DISABLED]
hdac0:            Name: audio mixer
hdac0:      Widget cap: 0x00200100
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=11 [audio selector] [DISABLED]
hdac0: 
hdac0:             nid: 16
hdac0:            Name: beep widget
hdac0:      Widget cap: 0x00700000
hdac0:     Association: -2 (0x00000000)
hdac0:             OSS: speaker (speaker)
hdac0: 
hdac0:             nid: 17 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=3 [audio output]
hdac0: 
hdac0:             nid: 18 [DISABLED]
---Type <return> to continue, or q <return> to quit---
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=8 [pin: Mic (Jack)]
hdac0: 
hdac0:             nid: 19 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=9 [pin: Line-in (Jack)]
hdac0: 
hdac0:             nid: 20 [DISABLED]
hdac0:            Name: power widget
hdac0:      Widget cap: 0x00500500
hdac0:                  PWR
hdac0:     connections: 13
hdac0:           |
hdac0:           + <- nid=13 [audio selector] [DISABLED] (selected)
hdac0:           + <- nid=14 [audio mixer] [DISABLED]
hdac0:           + <- nid=15 [audio mixer] [DISABLED]
hdac0:           + <- nid=16 [beep widget]
hdac0:           + <- nid=19 [audio selector] [DISABLED]
hdac0:           + <- nid=20 [power widget] [DISABLED]
hdac0:           + <- nid=21 [audio selector]
hdac0:           + <- nid=22 [pin: Digital-out (Fixed)] [DISABLED]
hdac0:           + <- nid=23 [pin: AUX (None)] [DISABLED]
hdac0:           + <- nid=24 [pin: Mic (Both)] [DISABLED]
hdac0:           + <- nid=25 [pin: CD (None)] [DISABLED]
hdac0:           + <- nid=26 [audio selector] [DISABLED]
hdac0:           + <- nid=29 [audio selector] [DISABLED]
hdac0: 
hdac0:             nid: 21
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
---Type <return> to continue, or q <return> to quit---
hdac0:                  STEREO
hdac0:     Association: 1 (0x00004001)
hdac0:             OSS: line, mic
hdac0:      Output amp: 0x80050f00
hdac0:                  mute=1 step=15 size=5 offset=0
hdac0:     connections: 8
hdac0:           |
hdac0:           + <- nid=12 [audio mixer] (selected)
hdac0:           + <- nid=9 [pin: Line-in (Jack)]
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0:           + [DISABLED] <- nid=15 [audio mixer] [DISABLED]
hdac0:           + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED]
hdac0:           + [DISABLED] <- nid=5 [pin: Speaker (Fixed)]
hdac0:           + [DISABLED] <- nid=24 [pin: Mic (Both)] [DISABLED]
hdac0:           + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED]
hdac0: 
hdac0:             nid: 22 [DISABLED]
hdac0:            Name: pin: Digital-out (Fixed)
hdac0:      Widget cap: 0x00400000
hdac0:         Pin cap: 0x00000020
hdac0:                  IN
hdac0:      Pin config: 0x995711f0
hdac0:     Pin control: 0x00000000
hdac0: 
hdac0:             nid: 23 [DISABLED]
hdac0:            Name: pin: AUX (None)
hdac0:      Widget cap: 0x00400081
hdac0:                  UNSOL STEREO
hdac0:         Pin cap: 0x00000027
hdac0:                  ISC TRQD PDC IN
hdac0:      Pin config: 0x5993e0f0
hdac0:     Pin control: 0x00000000
hdac0: 
hdac0:             nid: 24 [DISABLED]
hdac0:            Name: pin: Mic (Both)
hdac0:      Widget cap: 0x00400187
hdac0:                  UNSOL STEREO
hdac0:         Pin cap: 0x00001737
hdac0:                  ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ]
hdac0:      Pin config: 0xf0a79159
hdac0:     Pin control: 0x00000000
hdac0:      Output amp: 0x80053f3d
---Type <return> to continue, or q <return> to quit---
hdac0:                  mute=1 step=63 size=5 offset=61
hdac0:       Input amp: 0x00270300
hdac0:                  mute=0 step=3 size=39 offset=0
hdac0:     connections: 2
hdac0:           |
hdac0:           + [DISABLED] <- nid=3 [audio output] (selected)
hdac0:           + [DISABLED] <- nid=14 [audio mixer] [DISABLED]
hdac0: 
hdac0:             nid: 25 [DISABLED]
hdac0:            Name: pin: CD (None)
hdac0:      Widget cap: 0x00400001
hdac0:                  STEREO
hdac0:         Pin cap: 0x00000020
hdac0:                  IN
hdac0:      Pin config: 0x593310f0
hdac0:     Pin control: 0x00000000
hdac0: 
hdac0:             nid: 26 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=5 [pin: Speaker (Fixed)]
hdac0: 
hdac0:             nid: 27 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED]
hdac0: 
hdac0:             nid: 28 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
---Type <return> to continue, or q <return> to quit---
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=24 [pin: Mic (Both)] [DISABLED]
hdac0: 
hdac0:             nid: 29 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80051f17
hdac0:                  mute=1 step=31 size=5 offset=23
hdac0:     connections: 1
hdac0:           |
hdac0:           + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED]
hdac0: 
hdac0:             nid: 30
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:     Association: 1 (0x00000001)
hdac0:             OSS: mic
hdac0:      Output amp: 0x80000000
hdac0:                  mute=1 step=0 size=0 offset=0
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=8 [pin: Mic (Jack)]
hdac0: 
hdac0:             nid: 31 [DISABLED]
hdac0:            Name: audio selector
hdac0:      Widget cap: 0x0030010d
hdac0:                  STEREO
hdac0:      Output amp: 0x80000000
hdac0:                  mute=1 step=0 size=0 offset=0
hdac0:     connections: 1
hdac0:           |
hdac0:           + <- nid=24 [pin: Mic (Both)] [DISABLED]
hdac0: 
hdac0: Processing modem FG cad=1 nid=1...
hdac0: 
pcm0: <HDA Analog Devices AD1981HD PCM #0 Analog> at cad 0 nid 1 on hdac0
pcm0: +--------------------------------------+
pcm0: | DUMPING PCM Playback/Record Channels |
---Type <return> to continue, or q <return> to quit---
pcm0: +--------------------------------------+
pcm0: 
pcm0: Playback:
pcm0: 
pcm0:      Stream cap: 0x00000001
pcm0:                  PCM
pcm0:         PCM cap: 0x000e007f
pcm0:                  16 20 24 bits, 8 11 16 22 32 44 48 KHz
pcm0:             DAC: 3
pcm0: 
pcm0: Record:
pcm0: 
pcm0:      Stream cap: 0x00000001
pcm0:                  PCM
pcm0:         PCM cap: 0x0006007f
pcm0:                  16 20 bits, 8 11 16 22 32 44 48 KHz
pcm0:             ADC: 4
pcm0: 
pcm0: +--------------------------------+
pcm0: | DUMPING Playback/Record Pathes |
pcm0: +--------------------------------+
pcm0: 
pcm0: Playback:
pcm0: 
pcm0:     nid=5 [pin: Speaker (Fixed)]
pcm0:       |
pcm0:       + <- nid=3 [audio output] [src: pcm]
pcm0: 
pcm0:     nid=6 [pin: Headphones (Jack)]
pcm0:       |
pcm0:       + <- nid=3 [audio output] [src: pcm]
pcm0: 
pcm0: Record:
pcm0: 
pcm0:     nid=4 [audio input]
pcm0:       |
pcm0:       + <- nid=21 [audio selector] [src: line, mic]
pcm0:              |
pcm0:              + <- nid=12 [audio mixer] [src: mic]
pcm0:                     |
pcm0:                     + <- nid=30 [audio selector] [src: mic]
pcm0:                            |
---Type <return> to continue, or q <return> to quit---
pcm0:                            + <- nid=8 [pin: Mic (Jack)] [src: mic]
pcm0:              + <- nid=9 [pin: Line-in (Jack)] [src: line]
pcm0: 
pcm0: +-------------------------+
pcm0: | DUMPING Volume Controls |
pcm0: +-------------------------+
pcm0: 
pcm0: Master Volume (OSS: vol)
pcm0:    |
pcm0:    +- ctl  1 (nid   5 in ):    -91/3dB (64 steps) + mute
pcm0:    +- ctl  3 (nid   6 in ):    -91/3dB (64 steps) + mute
pcm0: 
pcm0: PCM Volume (OSS: pcm)
pcm0:    |
pcm0:    +- ctl  1 (nid   5 in ):    -91/3dB (64 steps) + mute
pcm0:    +- ctl  3 (nid   6 in ):    -91/3dB (64 steps) + mute
pcm0: 
pcm0: Microphone Volume (OSS: mic)
pcm0:    |
pcm0:    +- ctl  5 (nid   8 out):    0/30dB (4 steps)
pcm0:    +- ctl 19 (nid  30 out):    mute
pcm0: 
pcm0: Line-in Volume (OSS: line)
pcm0:    |
pcm0:    +- ctl  7 (nid   9 out):    0/30dB (4 steps)
pcm0: 
pcm0: Recording Level (OSS: rec)
pcm0:    |
pcm0:    +- ctl 12 (nid  21 out):    0/22dB (16 steps) + mute
pcm0:    +- ctl 19 (nid  30 out):    mute
pcm0: 
pcm0: Mixer "vol":
pcm0: Mixer "pcm":
pcm0: Mixer "line":
pcm0: Mixer "mic":
pcm0: Mixer "rec":
pcm0: Mixer "ogain":
pcm0: clone manager: deadline=750ms flags=0x8000001e
pcm0: sndbuf_setmap 1970000, 4000; 0xfffffffe78dc3000 -> 1970000
pcm0: sndbuf_setmap 1780000, 4000; 0xfffffffe78dd3000 -> 1780000
ATA PseudoRAID loaded
SMP: AP CPU #1 Launched!
---Type <return> to continue, or q <return> to quit---
cpu1 AP:
     ID: 0x01000000   VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff
  lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff
  timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00000400
ioapic0: Assigning ISA IRQ 1 to local APIC 0
ioapic0: Assigning ISA IRQ 9 to local APIC 1
ioapic0: Assigning ISA IRQ 12 to local APIC 0
ioapic0: Assigning ISA IRQ 14 to local APIC 1
ioapic0: Assigning PCI IRQ 16 to local APIC 0
ioapic0: Assigning PCI IRQ 17 to local APIC 1
ioapic0: Assigning PCI IRQ 20 to local APIC 0
ioapic0: Assigning PCI IRQ 23 to local APIC 1
msi: Assigning MSI IRQ 256 to local APIC 0
Trying to mount root from ufs:/dev/ad4s1a
WARNING: / was not properly dismounted
/: mount pending error: blocks 8 files 3
ct_to_ts([2008-12-16 19:33:55]) = 1229456035.000000000
start_init: trying /sbin/init
<118>Entropy harvesting: kickstart.
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
(probe0:ata0:0:0:0): error 22
(probe0:ata0:0:0:0): Unretryable Error
pass0 at ata0 bus 0 target 0 lun 0
pass0: <HL-DT-ST DVDRAM GSA-T20L NC08> Removable CD-ROM SCSI-0 device 
pass0: 16.000MB/s transfers
GEOM: new disk cd0
(cd0:ata0:0:0:0): error 6
(cd0:ata0:0:0:0): Unretryable Error
cd0 at ata0 bus 0 target 0 lun 0
cd0: <HL-DT-ST DVDRAM GSA-T20L NC08> Removable CD-ROM SCSI-0 device 
cd0: 16.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
(cd0:ata0:0:0:0): error 6
(cd0:ata0:0:0:0): Unretryable Error
(cd0:ata0:0:0:0): error 6
(cd0:ata0:0:0:0): Unretryable Error
(cd0:ata0:0:0:0): error 6
(cd0:ata0:0:0:0): Unretryable Error
(cd0:ata0:0:0:0): error 6
(cd0:ata0:0:0:0): Unretryable Error
acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0
acpi_tz0: _AC2: temperature 59.0 >= setpoint 50.0
---Type <return> to continue, or q <return> to quit---
acpi_tz0: switched from _AC1 to _AC2: 59.0C
acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
battery1: battery initialization failed, giving up
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
<118>/dev/ad4s1a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
<118>/dev/ad4s1a: SUMMARY INFORMATION BAD (SALVAGED)
<118>/dev/ad4s1a: BLK(S) MISSING IN BIT MAPS (SALVAGED)
<118>/dev/ad4s1a: 453034 files, 20740782 used, 53902307 free (100531 frags, 6725222 blocks, 0.1% fragmentation)
WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD.
<118>/etc/rc: WARNING: $hostname is not set -- see rc.conf(5).
<118>Starting Network: lo0.
<118>hw.bus.devctl_disable: 0 -> 1
<118>Additional TCP/IP options: tcp extensions=NO TCP keepalive=NO.
<118>savecore: reboot after panic: page fault
<118>savecore: writing core to vmcore.10
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
<118>Removing stale Samba tdb files:  done
<118>Configuring syscons: blanktime.
<118>Local package initialization:[: =: unexpected operator
acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0
<118>ipfw: :  (skipping /usr/local/etc/rc.d/kdm.sh, not executable) rtcLinux ELF exec handler installed
<118>.
<118>/etc/rc.d/sysctl: WARNING: sysctl dev.pcm.0.vchans does not exist.
<118>
<118>Tue Dec 16 19:36:18 MSK 2008
<118>date: : acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
---Type <return> to continue, or q <return> to quit---
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0
hdac0: wake_prep disabled wake for \_SB_.C08B.C0FD (S3)
pci0:1:5:0: Transition from D0 to D3
pci0:16:0:0: Transition from D0 to D3
vga0: saving 68 bytes of video state
pci0:0:18:0: Transition from D0 to D3
pci0:0:19:5: Transition from D0 to D3
pci0:0:20:2: Transition from D0 to D3
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0
acpi_tz0: switched from _AC2 to _AC3: 54.0C
ata2: reiniting channel ..
ata2: CONNECT requested
ata2: SATA connect time=0ms
ata2: BUSY wait time=1ms
ata2: SIGNATURE: 00000101
ata2: ahci_reset devices=00000001
ata2: CONNECTED
ata2: SATA connect time=0ms
ata2: BUSY wait time=1ms
ata2: SIGNATURE: 00000101
ata2: ahci_reset devices=00000001
ata2: identify ch->devices=00000001
ata2: reinit done ..
---Type <return> to continue, or q <return> to quit---
ata3: reiniting channel ..
ata3: port not implemented
ata3: reinit done ..
ata4: reiniting channel ..
ata4: port not implemented
ata4: reinit done ..
ata5: reiniting channel ..
ata5: port not implemented
ata5: reinit done ..
acpi_tz0: _AC2: temperature 56.0 >= setpoint 55.0
acpi_tz0: switched from _AC3 to _AC2: 56.0C
acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0
acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0
ata0: reiniting channel ..
ata0: reset tp1 mask=03 ostat0=00 ostat1=00
ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
ata0: reset tp2 stat0=00 stat1=00 devices=0x10000
ubt0: at uhub0 port 2 (addr 2) disconnected
ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire
ad: ad4 already exists; skipping it
ad: ad4 already exists; skipping it


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address	= 0x50
fault code		= supervisor read data, page not present
instruction pointer	= 0x8:0xffffffff80551631
stack pointer	        = 0x10:0xfffffffe4005bad0
frame pointer	        = 0x10:0xfffffffe4005bb20
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (thread taskq)
trap number		= 12
panic: page fault
cpuid = 1
Uptime: 6m23s
Physical memory: 1905 MB
Dumping 217 MB: 202 186 170 154 138 122 106 90 74 58 42 26 10(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) 
(kgdb) quit
HP# exit

exit

Script done on Tue Dec 16 19:50:51 2008
From Jeremy at FutureCIS.com  Wed Dec 17 13:00:02 2008
From: Jeremy at FutureCIS.com (Jeremy Gagliardi)
Date: Wed Dec 17 13:16:08 2008
Subject: amd64/129721: Motherboard K9N2G Neo-FD hangs on boot of 7.0-RELEASE
Message-ID: <200812172056.mBHKuce2080674@www.freebsd.org>


>Number:         129721
>Category:       amd64
>Synopsis:       Motherboard K9N2G Neo-FD hangs on boot of 7.0-RELEASE
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 17 21:00:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Jeremy Gagliardi
>Release:        7.0-RELEASE
>Organization:
Future CIS
>Environment:
Not able to boot, so can't really say.
>Description:
For the motherboard compatibility list at
http://www.freebsd.org/platforms/amd64/motherboards.html

Motherboard:  MSI K9N2G Neo-FD
Incompatible with FreeBSD 7.0-RELEASE
Hangs on boot, probably related to the NVIDIA NForce Storage Controller (thinks it's RocketRAID).  Chipset MCP78 (GeForce 8200) does not appear to be supported.
Thread...
http://www.nabble.com/FreeBSD-7-load-hangs-on-boot-tt21039625.html
>How-To-Repeat:
Try booting 7.0-RELEASE with this motherboard (any BIOS configuration--doesn't matter).
>Fix:
None.  Abandoned all hope.  Returned motherboard.

>Release-Note:
>Audit-Trail:
>Unformatted:
From yohimba at mail.ru  Thu Dec 18 23:02:10 2008
From: yohimba at mail.ru (Vyacheslav I.)
Date: Fri Dec 19 05:55:00 2008
Subject: Problem with FreeBSD for AMD64 & Mylex AcceleRAID
Message-ID: <E1LDZDJ-000Gxg-00.yohimba-mail-ru@f217.mail.ru>

Hi!

I used to use the FreeBSD on i386 architecture together with the controller Mylex AcceleRAID 170.There was RAID 0+1 configured on it out of 5 discs (Enhanced Mirroring).

# pciconf -lvc
...
mly0@pci0:6:1:0:        class=0x010400 card=0x00521069 chip=0x00501069 rev=0x02 hdr=0x00
    vendor     = 'Mylex Corp'
    device     = 'AcceleRAID Disk Array'
    class      = mass storage
    subclass   = RAID
    cap 01[80] = powerspec 2  supports D0 D3  current D0

I used this configuration on i386 architecture with the following versions FreeBSD: 4.x, 5.x, 6.x and 7.0. It always worked perfectly. But recently I got needed  8 GB RAM so I had to install the version FreeBSD for AMD64. First I tried the 7.0, and after all - RELENG_7_1 dated 12.12.2008. Both these systems work with the files system located on RAID unstabl?! Meanwhile the same hardware on i386 architecture works with RELENG_7_1 perfectly.

Hardware: MB INTEL DG33FB, CPU Intel(R) Core(TM)2 Quad CPU @ 2.40 GHz, RAM 8 GB.

The base system is installed on a separate IDE disc.

# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad4s1a    496M    111M    345M    24%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad4s1d    3.9G     22K    3.6G     0%    /tmp
/dev/ad4s1f    333G     52G    255G    17%    /usr
/dev/ad4s1e     15G     41M     14G     0%    /var
/dev/da0s1d   70.7G    410K   70.1G     0%    /mnt/da0/d

I carried out the following test by creating 3 big sized files of 1 GB each, and then deleting them:
# cd /mnt/da0/d
# dd if=/dev/zero of=test1 bs=1024k count=1024
# dd if=/dev/zero of=test2 bs=1024k count=1024
# dd if=/dev/zero of=test5 bs=1024k count=1024
# rm test*

After that I tried to unmount the files system, but I get a message of the kernel panic:
# cd /
# umount /mnt/da0/d

...
bad block 123456789, ino 176
dev = da0s1d, block = 4, fs = /mnt/da0/d
panic: ffs_blkfree: freeing free block
cpuid = 3
Uptime: 34 min...

The test was successful when using the i386 architecture with the same hardware

Taking a piece of advice of my friend, I used a dirty patch:
=== [code] ===
diff -Nru src.orig/sys/cam/scsi/scsi_da.c src/sys/cam/scsi/scsi_da.c
--- src.orig/sys/cam/scsi/scsi_da.c     2008-12-10 10:01:40.000000000 +0800
+++ src/sys/cam/scsi/scsi_da.c  2008-12-19 12:18:27.000000000 +0800
@@ -1187,7 +1187,7 @@
        if (match != NULL)
                softc->quirks = ((struct da_quirk_entry *)match)->quirks;
        else
-               softc->quirks = DA_Q_NONE;
+               softc->quirks = DA_Q_NO_SYNC_CACHE; // Dirty hack for AMD64

        /* Check if the SIM does not want 6 byte commands */
        xpt_setup_ccb(&cpi.ccb_h, periph->path, /*priority*/1);
=== [/code] ===

This patch solved the problem and the systems stopped being panicking. But I assume that this solution is wrong as the hardware works on i386 architecture without this patch well. 


From alias at jurrie.net  Sun Dec 21 00:20:04 2008
From: alias at jurrie.net (Jurriaan Nijkamp)
Date: Sun Dec 21 04:13:39 2008
Subject: amd64/129238: [panic] System randomly panics
Message-ID: <200812210820.mBL8K4JB017355@freefall.freebsd.org>

The following reply was made to PR amd64/129238; it has been noted by GNATS.

From: "Jurriaan Nijkamp" <alias@jurrie.net>
To: bug-followup@freebsd.org, alias@jurrie.net
Cc:  
Subject: Re: amd64/129238: [panic] System randomly panics
Date: Sun, 21 Dec 2008 09:14:42 +0100

 I switched the RAM from the server with some RAM from my desktop and the problem hasn't occurred since (little over two weeks). The RAM itself was fine, as is the main board, but apparantly they became instable when working together. A case of bad luck, I'd say.
 
 This report can be closed, as far as I'm concerned.
From linimon at FreeBSD.org  Sun Dec 21 09:25:17 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Sun Dec 21 09:33:29 2008
Subject: amd64/129238: [panic] System randomly panics
Message-ID: <200812211725.mBLHPFwi026491@freefall.freebsd.org>

Synopsis: [panic] System randomly panics

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sun Dec 21 17:25:03 UTC 2008
State-Changed-Why: 
Closed at submitter's request.

http://www.freebsd.org/cgi/query-pr.cgi?pr=129238
From bugmaster at FreeBSD.org  Mon Dec 22 03:06:48 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Dec 22 06:18:38 2008
Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org
Message-ID: <200812221106.mBMB6lGX060491@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/129721 amd64      [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R
o amd64/129667 amd64      [ata] Elitegroup A780GM-A IDE controller not recognize
o amd64/129488 amd64      [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: 
o amd64/129426 amd64      [panic] FreeBSD 7.0 crash after subdiskXX: detached
o amd64/129315 amd64      [boot] amd64 motherboard: Intel DG965WH motherboard co
f amd64/128978 amd64      [install] FreeBSD 6.3 64-bit  panics at boot time duri
o amd64/128810 amd64      AMD 64 port installation
o amd64/128765 amd64      [install] Install CD loads to Install choices but stop
o amd64/128686 amd64      [ata] can't detect SATA Disk on 8.0-Current with NF550
o amd64/128524 amd64      No geom documentation for loading gjournal
o amd64/128263 amd64      [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a
o amd64/128259 amd64      csh(1): "`" crashes csh
o amd64/128236 amd64      portsdb -Uu Indexing error
f kern/128102  amd64      AsusRock 939N68PV-GLAN not recognized
o amd64/127787 amd64      [lor] 3 lock LOR in recent CURRENT
o amd64/127640 amd64      GCC will not build shared libraries with -fprofile-gen
o amd64/127492 amd64      [zfs] System hang on ZFS input-output
o amd64/127484 amd64      [timecounters] Drift problem with FreeBSD 7.0 and 7.1 
o amd64/127451 amd64      [scheduler] incorrect load on quad core
o amd64/127397 amd64      [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI
s amd64/127276 amd64      ldd(1) invokes linux yes
o amd64/127129 amd64      mdconfig(8) is core dumping with Segmentation Fault 11
f amd64/125943 amd64      Serial Consoles do not work on amd64 freebsd
o amd64/125873 amd64      [smbd] [panic] Repeated kernel panics, trap 12 page fa
o amd64/125002 amd64      [install] amd64, SATA hard disks not detected
o amd64/124432 amd64      [panic] 7.0-STABLE panic: invalbuf: dirty bufs
o amd64/124134 amd64      [kernel] The kernel doesn't follow the calling convent
o amd64/123562 amd64      [install] FreeBSD amd64 not installs
o amd64/123520 amd64      [ahd] unable to boot from net while using ahd
o amd64/123456 amd64      fstat(1): /usr/bin/fstat shows error messages and hang
f amd64/123275 amd64      [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re
o kern/122782  amd64      [modules] accf_http.ko kernel module is not loadable
o amd64/122695 amd64      [cpufreq] Lack of cpufreq control using amd64 eith cor
o amd64/122624 amd64      unusable minimal installation of FreeBSD-7.0
o amd64/122549 amd64      7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial 
o amd64/122468 amd64      Compile problems after upgrading to 7.0
o amd64/122174 amd64      [panic] 7.0 no longer includes "device atpic" so fails
o amd64/121590 amd64      [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet
o amd64/121439 amd64      [boot] Installation of FreeBSD 7.0 fails: ACPI problem
o amd64/120202 amd64      [amd64] [patch] [panic] kernel panic at start_all_aps,
o amd64/119936 amd64      [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis
o amd64/119591 amd64      [amd64] [patch] time_t on 64-bit architecture
o amd64/117418 amd64      [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh
o amd64/117316 amd64      [acpi] ACPI lockups on SuperMicro motherboard
o amd64/117296 amd64      [ata] I don`t see second SATA IDE on VIA VT8237A
a amd64/117186 amd64      [modules] kldload Unsupported file type on STABLE amd6
s amd64/116689 amd64      [request] support for MSI K9MM-V
f amd64/116670 amd64      [ata] onboard SATA RAID1 controllers not supported for
o amd64/116620 amd64      [hang] ifconfig spins when creating carp(4) device on 
o amd64/116322 amd64      [panic] At start fsck on current, the system panics
o amd64/116159 amd64      [panic] Panic while debugging on CURRENT
s amd64/115815 amd64      [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp
o amd64/115581 amd64      [Makefile] [patch] -mfancy-math-387 has no effect
o amd64/115194 amd64      LCD screen remains blank after Dell XPS M1210 lid is c
o amd64/114270 amd64      [cpufreq] cpufreq doesnt work when compiled in to kern
o amd64/114111 amd64      [nfs] System crashes while writing on NFS-mounted shar
f amd64/113021 amd64      [re] ASUS M2A-VM onboard NIC does not work
o amd64/112222 amd64      [libc] 32-bit libc incorrectly converts some FP number
f amd64/111992 amd64      [boot] BTX failed - HP Laptop dv2315nr
o amd64/110655 amd64      [threads] 32 bit threaded applications crash on amd64 
o amd64/110599 amd64      [geli] geli attach to gmirror device hangs and cannot 
s amd64/108861 amd64      [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work
o amd64/106186 amd64      [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p
f amd64/105629 amd64      [re] TrendNet TEG-BUSR 10/100/1000 disables itself on 
f amd64/105531 amd64      [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does
f amd64/105514 amd64      [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv
o amd64/102716 amd64      ex with no argument in an xterm gets SIGSEGV
o amd64/97337  amd64      [dri] xorg reboots system if dri module is enabled
o amd64/95888  amd64      [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP 
f amd64/94989  amd64      [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64)
o amd64/94677  amd64      [panic] panic in amd64 install at non-root user creati
o amd64/93961  amd64      [busdma] Problem in bounce buffer handling in sys/amd6
o amd64/92337  amd64      [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff
f amd64/91492  amd64      [boot] BTX halted
o amd64/91405  amd64      [asr] [panic] Kernel panic caused by asr on 6.0-amd64 
o amd64/89501  amd64      [install] System crashes on install using ftp on local
o amd64/88790  amd64      [panic] kernel panic on first boot (after the FreeBSD 
o amd64/88568  amd64      [panic] 6.0-RELEASE install cd does not boot with usb 
o amd64/87689  amd64      [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE
o amd64/87316  amd64      [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6
o amd64/87305  amd64      [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in
f amd64/87258  amd64      [smp] [boot] cannot boot with SMP and Areca ARC-1160 r
f amd64/86080  amd64      [radeon] [hang] radeon DRI causes system hang on amd64
s amd64/85273  amd64      [install] FreeBSD (NetBSD or OpenBSD) not install on l
o amd64/78406  amd64      [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys
o amd64/76136  amd64      [hang] system halts before reboot
o amd64/74747  amd64      [panic] System panic on shutdown when process will not
o amd64/73322  amd64      [msdosfs] [hang] unarchiving /etc to msdosfs locks up 

88 problems total.

From yanefbsd at gmail.com  Mon Dec 22 21:59:38 2008
From: yanefbsd at gmail.com (Garrett Cooper)
Date: Tue Dec 23 05:51:22 2008
Subject: -m32 broken on bi-arch amd64 systems?
Message-ID: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>

Hi guys,
    I think I may have found an issue today with our bi-endian
structure, and I wanted to make sure whether or not it was an already
known issue (-m32 is broken for gcc with lib32/libgcc.a):

[root@fbsd-7-test]# gcc -o boo boo.c # Compiles
[root@fbsd-7-test]# gcc -m32 -o boo boo.c
/usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc
/usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
[root@fbsd-7-test]# file /usr/lib32/libgcc_s.so.1
/usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
version 1 (FreeBSD), dynamically linked, stripped
[root@fbsd-7-test]# uname -a
FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD
7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008
root@fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR  amd64

    I wish I had my amd64 CURRENT machine in front of me to confirm
this, but I don't.
    Please keep me CC'ed as I am not subscribed to either amd64@ or stable@.
Thanks!
-Garrett
From maciej at suszko.eu  Tue Dec 23 09:02:59 2008
From: maciej at suszko.eu (Maciej Suszko)
Date: Tue Dec 23 09:03:14 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
Message-ID: <20081223173608.068fe9d8@suszko.eu>

"Garrett Cooper" <yanefbsd@gmail.com> wrote:
> Hi guys,
>     I think I may have found an issue today with our bi-endian
> structure, and I wanted to make sure whether or not it was an already
> known issue (-m32 is broken for gcc with lib32/libgcc.a):
> 
> [root@fbsd-7-test]# gcc -o boo boo.c # Compiles
> [root@fbsd-7-test]# gcc -m32 -o boo boo.c
> /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching
> for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when
> searching for -lgcc /usr/bin/ld: cannot find -lgcc
> [root@fbsd-7-test]# file /usr/lib32/libgcc_s.so.1
> /usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
> version 1 (FreeBSD), dynamically linked, stripped
> [root@fbsd-7-test]# uname -a
> FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD
> 7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008
> root@fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR  amd64
> 
>     I wish I had my amd64 CURRENT machine in front of me to confirm
> this, but I don't.
>     Please keep me CC'ed as I am not subscribed to either amd64@ or
> stable@. Thanks!
> -Garrett

I also noticed that behavior, shouldn't compiler/linker look
into /usr/lib32 without additional -B switch?
-- 
regards, Maciej Suszko.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081223/d2044bbe/signature.pgp
From maciej at suszko.eu  Tue Dec 23 09:02:59 2008
From: maciej at suszko.eu (Maciej Suszko)
Date: Tue Dec 23 09:03:14 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
Message-ID: <20081223173608.068fe9d8@suszko.eu>

"Garrett Cooper" <yanefbsd@gmail.com> wrote:
> Hi guys,
>     I think I may have found an issue today with our bi-endian
> structure, and I wanted to make sure whether or not it was an already
> known issue (-m32 is broken for gcc with lib32/libgcc.a):
> 
> [root@fbsd-7-test]# gcc -o boo boo.c # Compiles
> [root@fbsd-7-test]# gcc -m32 -o boo boo.c
> /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching
> for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when
> searching for -lgcc /usr/bin/ld: cannot find -lgcc
> [root@fbsd-7-test]# file /usr/lib32/libgcc_s.so.1
> /usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
> version 1 (FreeBSD), dynamically linked, stripped
> [root@fbsd-7-test]# uname -a
> FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD
> 7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008
> root@fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR  amd64
> 
>     I wish I had my amd64 CURRENT machine in front of me to confirm
> this, but I don't.
>     Please keep me CC'ed as I am not subscribed to either amd64@ or
> stable@. Thanks!
> -Garrett

I also noticed that behavior, shouldn't compiler/linker look
into /usr/lib32 without additional -B switch?
-- 
regards, Maciej Suszko.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081223/d2044bbe/signature-0001.pgp
From kabaev at gmail.com  Tue Dec 23 09:50:26 2008
From: kabaev at gmail.com (Alexander Kabaev)
Date: Tue Dec 23 09:50:33 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <20081223173608.068fe9d8@suszko.eu>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
Message-ID: <20081223122313.6254e173@kan.dnsalias.net>

On Tue, 23 Dec 2008 17:36:08 +0100
Maciej Suszko <maciej@suszko.eu> wrote:

> "Garrett Cooper" <yanefbsd@gmail.com> wrote:
> > Hi guys,
> >     I think I may have found an issue today with our bi-endian
> > structure, and I wanted to make sure whether or not it was an
> > already known issue (-m32 is broken for gcc with lib32/libgcc.a):
> > 
> > [root@fbsd-7-test]# gcc -o boo boo.c # Compiles
> > [root@fbsd-7-test]# gcc -m32 -o boo boo.c
> > /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching
> > for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when
> > searching for -lgcc /usr/bin/ld: cannot find -lgcc
> > [root@fbsd-7-test]# file /usr/lib32/libgcc_s.so.1
> > /usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
> > version 1 (FreeBSD), dynamically linked, stripped
> > [root@fbsd-7-test]# uname -a
> > FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD
> > 7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008
> > root@fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR  amd64
> > 
> >     I wish I had my amd64 CURRENT machine in front of me to confirm
> > this, but I don't.
> >     Please keep me CC'ed as I am not subscribed to either amd64@ or
> > stable@. Thanks!
> > -Garrett
> 
> I also noticed that behavior, shouldn't compiler/linker look
> into /usr/lib32 without additional -B switch?
> -- 
> regards, Maciej Suszko.

Read email archives, this was discussed on several occasions before.
Short summary: it never worked and will not work unless some
non-trivial work is put into how GCC handles include and linker search
paths.

-- 
Alexander Kabaev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20081223/17c56970/signature.pgp
From wieczyk at gmail.com  Tue Dec 23 10:08:22 2008
From: wieczyk at gmail.com (=?ISO-8859-2?Q?Pawe=B3_Wieczorek?=)
Date: Tue Dec 23 10:08:29 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
Message-ID: <1255bf0d0812230946nc90ee38u28b040c3d720868a@mail.gmail.com>

I will extend topic to C++:

[19:38] zubr:~/Code (1) $ g++ -m32 -B /usr/lib32 p.cpp
In file included from /usr/include/c++/4.2/ext/new_allocator.h:37,
                 from /usr/include/c++/4.2/bits/c++allocator.h:39,
                 from /usr/include/c++/4.2/bits/allocator.h:53,
                 from /usr/include/c++/4.2/memory:54,
                 from /usr/include/c++/4.2/string:48,
                 from /usr/include/c++/4.2/bits/locale_classes.h:47,
                 from /usr/include/c++/4.2/bits/ios_base.h:47,
                 from /usr/include/c++/4.2/ios:48,
                 from /usr/include/c++/4.2/ostream:45,
                 from /usr/include/c++/4.2/iostream:45,
                 from p.cpp:1:
/usr/include/c++/4.2/new:95: error: 'operator new' takes type 'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:96: error: 'operator new' takes type 'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:99: error: 'operator new' takes type 'size_t'
('unsigned int') as first parameter
/usr/include/c++/4.2/new:100: error: 'operator new' takes type
'size_t' ('unsigned int') as first parameter
/usr/include/c++/4.2/new:105: error: 'operator new' takes type
'size_t' ('unsigned int') as first parameter
/usr/include/c++/4.2/new:106: error: 'operator new' takes type
'size_t' ('unsigned int') as first parameter
[19:38] zubr:~/Code (1) $ cat p.cpp
#include <iostream>

int
main()
{
    return 0;
}

[19:39] zubr:~/Code $

Problem with C++ is more connected to headers than binaries, any suggestions
how to use G++ to produce 32bit code ?
From josh.carroll at gmail.com  Tue Dec 23 10:23:54 2008
From: josh.carroll at gmail.com (Josh Carroll)
Date: Tue Dec 23 10:32:25 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <20081223173608.068fe9d8@suszko.eu>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
Message-ID: <8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>

> I also noticed that behavior, shouldn't compiler/linker look
> into /usr/lib32 without additional -B switch?
> --
> regards, Maciej Suszko.
>

I don't know if it should or should not, but I can confirm that this
behavior was around in 7.0-RELEASE, so it's been that way for quite a
while, at least in the 7 branch.

Josh
From sgk at troutmask.apl.washington.edu  Tue Dec 23 10:36:49 2008
From: sgk at troutmask.apl.washington.edu (Steve Kargl)
Date: Tue Dec 23 10:37:02 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
	<8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>
Message-ID: <20081223183649.GA90840@troutmask.apl.washington.edu>

On Tue, Dec 23, 2008 at 12:55:04PM -0500, Josh Carroll wrote:
> > I also noticed that behavior, shouldn't compiler/linker look
> > into /usr/lib32 without additional -B switch?
> > --
> > regards, Maciej Suszko.
> >
> 
> I don't know if it should or should not, but I can confirm that this
> behavior was around in 7.0-RELEASE, so it's been that way for quite a
> while, at least in the 7 branch.
> 

Sigh.  Read the list archives.  It's been this way since Peter
Wemm first introduce the ability to run i386 binaries on 
amd64.

-- 
Steve
From c_tolis at otenet.gr  Tue Dec 23 12:40:04 2008
From: c_tolis at otenet.gr (Christos)
Date: Tue Dec 23 14:06:26 2008
Subject: amd64/129889: The booting process stops at the line mounting root
	ufs /dev/md0 (Starting with the option for no acpi )
Message-ID: <200812232032.mBNKWZKS036734@www.freebsd.org>


>Number:         129889
>Category:       amd64
>Synopsis:       The booting process  stops at the line mounting root ufs /dev/md0 (Starting with the option for no acpi )
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 23 20:40:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Christos
>Release:        7.0
>Organization:
-
>Environment:
>Description:
The booting process  stops at the line mounting root ufs /dev/md0 (Starting with the option for no acpi )

Can't boot or install the freebsd 7.0 or the pcbsd 
I have Amd athlon 64x2 2.6 , 3gb ram  , sapphire motherboard and one sata and one ide hard disk, Nvidia graphics card.

c_tolis@otenet.gr

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From yanefbsd at gmail.com  Tue Dec 23 13:08:09 2008
From: yanefbsd at gmail.com (Garrett Cooper)
Date: Tue Dec 23 14:06:35 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <20081223183649.GA90840@troutmask.apl.washington.edu>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
	<8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>
	<20081223183649.GA90840@troutmask.apl.washington.edu>
Message-ID: <A2C23373-71BE-4492-B3AD-42F4F25ED09A@gmail.com>

On Dec 23, 2008, at 10:36, Steve Kargl  
<sgk@troutmask.apl.washington.edu> wrote:

> On Tue, Dec 23, 2008 at 12:55:04PM -0500, Josh Carroll wrote:
>>> I also noticed that behavior, shouldn't compiler/linker look
>>> into /usr/lib32 without additional -B switch?
>>> --
>>> regards, Maciej Suszko.
>>>
>>
>> I don't know if it should or should not, but I can confirm that this
>> behavior was around in 7.0-RELEASE, so it's been that way for quite a
>> while, at least in the 7 branch.
>>
>
> Sigh.  Read the list archives.  It's been this way since Peter
> Wemm first introduce the ability to run i386 binaries on
> amd64.
>
> -- 
> Steve

Ok, let's bury this topic then.
Thanks for the confirmation and sorry for the noise.
-Garrett
From peter at wemm.org  Tue Dec 23 16:27:01 2008
From: peter at wemm.org (Peter Wemm)
Date: Tue Dec 23 16:27:07 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <A2C23373-71BE-4492-B3AD-42F4F25ED09A@gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
	<8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>
	<20081223183649.GA90840@troutmask.apl.washington.edu>
	<A2C23373-71BE-4492-B3AD-42F4F25ED09A@gmail.com>
Message-ID: <e7db6d980812231554q58a3324fh7de1f1cb0b170dd5@mail.gmail.com>

On Tue, Dec 23, 2008 at 1:07 PM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> On Dec 23, 2008, at 10:36, Steve Kargl <sgk@troutmask.apl.washington.edu>
> wrote:
>
>> On Tue, Dec 23, 2008 at 12:55:04PM -0500, Josh Carroll wrote:
>>>>
>>>> I also noticed that behavior, shouldn't compiler/linker look
>>>> into /usr/lib32 without additional -B switch?
>>>> --
>>>> regards, Maciej Suszko.
>>>>
>>>
>>> I don't know if it should or should not, but I can confirm that this
>>> behavior was around in 7.0-RELEASE, so it's been that way for quite a
>>> while, at least in the 7 branch.
>>>
>>
>> Sigh.  Read the list archives.  It's been this way since Peter
>> Wemm first introduce the ability to run i386 binaries on
>> amd64.
>>
>> --
>> Steve
>
> Ok, let's bury this topic then.
> Thanks for the confirmation and sorry for the noise.
> -Garrett

A patch can be extraced from
  http://people.freebsd.org/~peter/hammer.diff
that makes it "work", but its not right.  It doesn't quite do -I
include overrides right when -m32 is specified.

It's enough to make just about everything else work.  I forgot that I
was building valgrind with it for some time now.

-- 
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV
"All of this is for nothing if we don't go to the stars" - JMS/B5
"If Java had true garbage collection, most programs would delete
themselves upon execution." -- Robert Sewell
From bruce at cran.org.uk  Thu Dec 25 13:10:03 2008
From: bruce at cran.org.uk (Bruce Cran)
Date: Thu Dec 25 13:10:10 2008
Subject: amd64/127640: GCC will not build shared libraries with
 -fprofile-generate on amd64
Message-ID: <200812252110.mBPLA3jP073441@freefall.freebsd.org>

The following reply was made to PR amd64/127640; it has been noted by GNATS.

From: Bruce Cran <bruce@cran.org.uk>
To: bug-followup@FreeBSD.org, zlynx@acm.org
Cc:  
Subject: Re: amd64/127640: GCC will not build shared libraries with
 -fprofile-generate on amd64
Date: Thu, 25 Dec 2008 21:03:37 +0000

 I think the problem isn't that the application isn't being built with
 -fPIC, but that libgcov.a hasn't been built with it.  Running a 'make'
 in /usr/src/gnu/lib/libgcov shows libgcov.c being built without that
 flag, despite the following being present in the Makefile:
 
 $(OBJS_T}: libgcov.c
 	${CC} -c ${CFLAGS} -DL${.PREFIX} -o ${.TARGET} ${.ALLSRC:M*.c}
 
 .if !defined(NO_PIC)
 ${OBJS_S}: libgcov.c
 	${CC} -c ${PICFLAG} ${CFLAGS} -DL${.PREFIX} -o ${.TARGET}
 ${.ALLSRC:M*.c}
 .endif
 
 --
 Bruce Cran
From yanefbsd at gmail.com  Fri Dec 26 19:09:13 2008
From: yanefbsd at gmail.com (Garrett Cooper)
Date: Fri Dec 26 20:44:28 2008
Subject: -m32 broken on bi-arch amd64 systems?
In-Reply-To: <e7db6d980812231554q58a3324fh7de1f1cb0b170dd5@mail.gmail.com>
References: <7d6fde3d0812222135l753daf54geb37b696c9c1cf8@mail.gmail.com>
	<20081223173608.068fe9d8@suszko.eu>
	<8cb6106e0812230955u1bd16932h7ae4ad3fc8c97f28@mail.gmail.com>
	<20081223183649.GA90840@troutmask.apl.washington.edu>
	<A2C23373-71BE-4492-B3AD-42F4F25ED09A@gmail.com>
	<e7db6d980812231554q58a3324fh7de1f1cb0b170dd5@mail.gmail.com>
Message-ID: <7d6fde3d0812261909x5fafc017ubab2317d8852cb73@mail.gmail.com>

On Tue, Dec 23, 2008 at 3:54 PM, Peter Wemm <peter@wemm.org> wrote:
> On Tue, Dec 23, 2008 at 1:07 PM, Garrett Cooper <yanefbsd@gmail.com> wrote:
>> On Dec 23, 2008, at 10:36, Steve Kargl <sgk@troutmask.apl.washington.edu>
>> wrote:
>>
>>> On Tue, Dec 23, 2008 at 12:55:04PM -0500, Josh Carroll wrote:
>>>>>
>>>>> I also noticed that behavior, shouldn't compiler/linker look
>>>>> into /usr/lib32 without additional -B switch?
>>>>> --
>>>>> regards, Maciej Suszko.
>>>>>
>>>>
>>>> I don't know if it should or should not, but I can confirm that this
>>>> behavior was around in 7.0-RELEASE, so it's been that way for quite a
>>>> while, at least in the 7 branch.
>>>>
>>>
>>> Sigh.  Read the list archives.  It's been this way since Peter
>>> Wemm first introduce the ability to run i386 binaries on
>>> amd64.
>>>
>>> --
>>> Steve
>>
>> Ok, let's bury this topic then.
>> Thanks for the confirmation and sorry for the noise.
>> -Garrett
>
> A patch can be extraced from
>  http://people.freebsd.org/~peter/hammer.diff
> that makes it "work", but its not right.  It doesn't quite do -I
> include overrides right when -m32 is specified.
>
> It's enough to make just about everything else work.  I forgot that I
> was building valgrind with it for some time now.

I'll give that a shot, provide some feedback, and see if I can *maybe*
(shrugs) improve upon it.
Thanks Peter!
-Garrett
From tinderbox at freebsd.org  Sat Dec 27 03:46:25 2008
From: tinderbox at freebsd.org (FreeBSD Tinderbox)
Date: Sat Dec 27 03:46:43 2008
Subject: [head tinderbox] failure on amd64/amd64
Message-ID: <20081227114622.D93B77302F@freebsd-current.sentex.ca>

TB --- 2008-12-27 09:20:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2008-12-27 09:20:01 - starting HEAD tinderbox run for amd64/amd64
TB --- 2008-12-27 09:20:01 - cleaning the object tree
TB --- 2008-12-27 09:21:04 - cvsupping the source tree
TB --- 2008-12-27 09:21:04 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2008-12-27 09:21:12 - building world
TB --- 2008-12-27 09:21:12 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-27 09:21:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-27 09:21:12 - TARGET=amd64
TB --- 2008-12-27 09:21:12 - TARGET_ARCH=amd64
TB --- 2008-12-27 09:21:12 - TZ=UTC
TB --- 2008-12-27 09:21:12 - __MAKE_CONF=/dev/null
TB --- 2008-12-27 09:21:12 - cd /src
TB --- 2008-12-27 09:21:12 - /usr/bin/make -B buildworld
>>> World build started on Sat Dec 27 09:21:14 UTC 2008
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> stage 5.1: building 32 bit shim libraries
>>> World build completed on Sat Dec 27 11:18:59 UTC 2008
TB --- 2008-12-27 11:18:59 - generating LINT kernel config
TB --- 2008-12-27 11:18:59 - cd /src/sys/amd64/conf
TB --- 2008-12-27 11:18:59 - /usr/bin/make -B LINT
TB --- 2008-12-27 11:18:59 - building LINT kernel
TB --- 2008-12-27 11:18:59 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-27 11:18:59 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-27 11:18:59 - TARGET=amd64
TB --- 2008-12-27 11:18:59 - TARGET_ARCH=amd64
TB --- 2008-12-27 11:18:59 - TZ=UTC
TB --- 2008-12-27 11:18:59 - __MAKE_CONF=/dev/null
TB --- 2008-12-27 11:18:59 - cd /src
TB --- 2008-12-27 11:18:59 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Sat Dec 27 11:18:59 UTC 2008
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
awk -f /src/sys/modules/usb2/misc_fm/../../../conf/kmod_syms.awk usb2_misc_fm.ko  export_syms | xargs -J% objcopy % usb2_misc_fm.ko
objcopy --strip-debug usb2_misc_fm.ko
===> usb2/ndis (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common  -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/usb2_ndis.c
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common  -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/if_ndis_usb2.c
In file included from /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/if_ndis_usb2.c:60:
@/dev/if_ndis/if_ndisvar.h:121: error: expected specifier-qualifier-list before 'usbd_xfer_handle'
@/dev/if_ndis/if_ndisvar.h:212: error: expected specifier-qualifier-list before 'usbd_pipe_handle'
*** Error code 1

Stop in /src/sys/modules/usb2/ndis.
*** Error code 1

Stop in /src/sys/modules/usb2.
*** Error code 1

Stop in /src/sys/modules.
*** Error code 1

Stop in /obj/amd64/src/sys/LINT.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-12-27 11:46:22 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-12-27 11:46:22 - ERROR: failed to build lint kernel
TB --- 2008-12-27 11:46:22 - 6959.62 user 668.50 system 8781.59 real


http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full
From weongyo.jeong at gmail.com  Sat Dec 27 04:57:46 2008
From: weongyo.jeong at gmail.com (Weongyo Jeong)
Date: Sat Dec 27 06:04:54 2008
Subject: [head tinderbox] failure on amd64/amd64
In-Reply-To: <20081227114622.D93B77302F@freebsd-current.sentex.ca>
References: <20081227114622.D93B77302F@freebsd-current.sentex.ca>
Message-ID: <20081227122544.GA2561@freebsd.weongyo.org>

On Sat, Dec 27, 2008 at 06:46:22AM -0500, FreeBSD Tinderbox wrote:
> TB --- 2008-12-27 09:20:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
> TB --- 2008-12-27 09:20:01 - starting HEAD tinderbox run for amd64/amd64
> TB --- 2008-12-27 09:20:01 - cleaning the object tree
> TB --- 2008-12-27 09:21:04 - cvsupping the source tree
> TB --- 2008-12-27 09:21:04 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile
> TB --- 2008-12-27 09:21:12 - building world
> TB --- 2008-12-27 09:21:12 - MAKEOBJDIRPREFIX=/obj
> TB --- 2008-12-27 09:21:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
> TB --- 2008-12-27 09:21:12 - TARGET=amd64
> TB --- 2008-12-27 09:21:12 - TARGET_ARCH=amd64
> TB --- 2008-12-27 09:21:12 - TZ=UTC
> TB --- 2008-12-27 09:21:12 - __MAKE_CONF=/dev/null
> TB --- 2008-12-27 09:21:12 - cd /src
> TB --- 2008-12-27 09:21:12 - /usr/bin/make -B buildworld
> >>> World build started on Sat Dec 27 09:21:14 UTC 2008
> >>> Rebuilding the temporary build tree
> >>> stage 1.1: legacy release compatibility shims
> >>> stage 1.2: bootstrap tools
> >>> stage 2.1: cleaning up the object tree
> >>> stage 2.2: rebuilding the object tree
> >>> stage 2.3: build tools
> >>> stage 3: cross tools
> >>> stage 4.1: building includes
> >>> stage 4.2: building libraries
> >>> stage 4.3: make dependencies
> >>> stage 4.4: building everything
> >>> stage 5.1: building 32 bit shim libraries
> >>> World build completed on Sat Dec 27 11:18:59 UTC 2008
> TB --- 2008-12-27 11:18:59 - generating LINT kernel config
> TB --- 2008-12-27 11:18:59 - cd /src/sys/amd64/conf
> TB --- 2008-12-27 11:18:59 - /usr/bin/make -B LINT
> TB --- 2008-12-27 11:18:59 - building LINT kernel
> TB --- 2008-12-27 11:18:59 - MAKEOBJDIRPREFIX=/obj
> TB --- 2008-12-27 11:18:59 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
> TB --- 2008-12-27 11:18:59 - TARGET=amd64
> TB --- 2008-12-27 11:18:59 - TARGET_ARCH=amd64
> TB --- 2008-12-27 11:18:59 - TZ=UTC
> TB --- 2008-12-27 11:18:59 - __MAKE_CONF=/dev/null
> TB --- 2008-12-27 11:18:59 - cd /src
> TB --- 2008-12-27 11:18:59 - /usr/bin/make -B buildkernel KERNCONF=LINT
> >>> Kernel build for LINT started on Sat Dec 27 11:18:59 UTC 2008
> >>> stage 1: configuring the kernel
> >>> stage 2.1: cleaning up the object tree
> >>> stage 2.2: rebuilding the object tree
> >>> stage 2.3: build tools
> >>> stage 3.1: making dependencies
> >>> stage 3.2: building everything
> [...]
> awk -f /src/sys/modules/usb2/misc_fm/../../../conf/kmod_syms.awk usb2_misc_fm.ko  export_syms | xargs -J% objcopy % usb2_misc_fm.ko
> objcopy --strip-debug usb2_misc_fm.ko
> ===> usb2/ndis (all)
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common  -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/usb2_ndis.c
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common  -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/if_ndis_usb2.c
> In file included from /src/sys/modules/usb2/ndis/../../../dev/usb2/ndis/if_ndis_usb2.c:60:
> @/dev/if_ndis/if_ndisvar.h:121: error: expected specifier-qualifier-list before 'usbd_xfer_handle'
> @/dev/if_ndis/if_ndisvar.h:212: error: expected specifier-qualifier-list before 'usbd_pipe_handle'
> *** Error code 1
> 
> Stop in /src/sys/modules/usb2/ndis.
> *** Error code 1
> 
> Stop in /src/sys/modules/usb2.
> *** Error code 1
> 
> Stop in /src/sys/modules.
> *** Error code 1
> 
> Stop in /obj/amd64/src/sys/LINT.
> *** Error code 1
> 
> Stop in /src.
> *** Error code 1
> 
> Stop in /src.
> TB --- 2008-12-27 11:46:22 - WARNING: /usr/bin/make returned exit code  1 
> TB --- 2008-12-27 11:46:22 - ERROR: failed to build lint kernel
> TB --- 2008-12-27 11:46:22 - 6959.62 user 668.50 system 8781.59 real

It should be fixed now.  Sorry for a disturbance.

regards,
Weongyo Jeong

From naliyev at ultel.az  Sat Dec 27 09:23:01 2008
From: naliyev at ultel.az (Nadir M. Aliyev)
Date: Sat Dec 27 10:06:01 2008
Subject: bug: smart array p400
Message-ID: <20081227170346.42881444DCD@mail.ultel.net>

 

Hi. i have server HP Proliant DL380 G5 Storage Rack server. with 2x Intel
Xeon 2.5 Ghz, 10 GB of RAM, 6 SAS (RAID5+ONLINE SPARE)and Smart Array P400
with 256 mb memory. i installed 64 bit version and have a great problems:

 

 

i can install FreeBSD64bit in normal mode. without bootmanager (64 bit cant
loads with bootmanager :( )

 

But i can not load/install system ACPI or safe mode. 

Sometimes its fault issues while server working and then rebooting
automacily.

 

This is error code:

ciss0: <HP Smart Array P400> port0x4000 mem
0xfde00000-0xfdefffff,0xfddf0000-0xfddf0fff irq 10 ad device 0.0 on pci6

ciss can't allocate interrupt

 

Fatal trap 12: page fault while in kernel mode

cpuid = 0; apic id       = 00

fault virtual address   = 0x30

fault code                 = supervisor read data, page not present

instruction pointer:    = 0x8:0xffffffff80487e2f

stack pointer             = 0x10:0xffffffff80af3850

frame pointer            = 0x10:0xffffffff8098bd50

code segment           = base 0x0, limit 0xfffff, type 0x1b

                                = DPL 0, pres 1, long 1, def32 0, gran 1

processor eflags       = resume, IOPL = 0

current process         = 0 (swaper)

trap number              = 12

panic: page fault

 

 

---

This bug issues with freebsd 64bit 7.0 and 7.1 rc2. 

 

but i tried 32 bit freebsd 7.0 and i can load system with ACPI and normal
mode. 

 

Please help me how can i fix this problem.

Great Thanks

 

 

 

 

 

* * * 
Nadir Aliyev  
System and Unix Administrator
ULTEL LTD. Internet & Information Technologies Department 
14 M.Mekhti-zade. Baku, Azerbaijan AZ1023 

Work:     +994(12) 4967199
Mobile:    +994(55) 7012310
www:        <http://www.ultel.az> http://www.ultel.az 

 

From kometen at gmail.com  Sat Dec 27 13:12:57 2008
From: kometen at gmail.com (Claus Guttesen)
Date: Sat Dec 27 13:13:04 2008
Subject: bug: smart array p400
In-Reply-To: <20081227170346.42881444DCD@mail.ultel.net>
References: <20081227170346.42881444DCD@mail.ultel.net>
Message-ID: <b41c75520812271251x7039f9d8v3f1b59d70be1dafb@mail.gmail.com>

> Hi. i have server HP Proliant DL380 G5 Storage Rack server. with 2x Intel
> Xeon 2.5 Ghz, 10 GB of RAM, 6 SAS (RAID5+ONLINE SPARE)and Smart Array P400
> with 256 mb memory. i installed 64 bit version and have a great problems:
>
> i can install FreeBSD64bit in normal mode. without bootmanager (64 bit cant
> loads with bootmanager :( )
>
> But i can not load/install system ACPI or safe mode.
>
> Sometimes its fault issues while server working and then rebooting
> automacily.
>
> This bug issues with freebsd 64bit 7.0 and 7.1 rc2.
>
> but i tried 32 bit freebsd 7.0 and i can load system with ACPI and normal
> mode.

Hmm, strange. I have both DL 360 and 380 G5's (and blade-servers) with
64, 256 and 512 MB ciss-controllers, either as webservers or as
db-server and all are working flawlessly with the amd64. The db-server
is running 7.0 release and the webservers are running a 7.1 beta-2
version.

How old is the server in question? Maby you need to update the bios?

-- 
regards
Claus

When lenity and cruelty play for a kingdom,
the gentler gamester is the soonest winner.

Shakespeare
From nti at w4w.net  Sun Dec 28 10:00:11 2008
From: nti at w4w.net (Nicola Tiling)
Date: Sun Dec 28 10:07:28 2008
Subject: amd64/117186: [modules] kldload Unsupported file type on STABLE
	amd64
Message-ID: <200812281800.mBSI04RO090703@freefall.freebsd.org>

The following reply was made to PR amd64/117186; it has been noted by GNATS.

From: Nicola Tiling <nti@w4w.net>
To: bug-followup@FreeBSD.org,
 sean@mcneil.com
Cc:  
Subject: Re: amd64/117186: [modules] kldload Unsupported file type on STABLE amd64
Date: Sun, 28 Dec 2008 18:39:26 +0100

 Hi
 
 Bug still exists on 6.4-STABLE FreeBSD amd64 build Sat Dec 27 23:51 2008
 
 from dmesg:
 
 kldload: /boot/kernel/fdescfs.ko: Unsupported file type
 kldload: /boot/kernel/pflog.ko: Unsupported file type
 kldload: /boot/kernel/pf.ko: Unsupported file type
 kldload: /boot/kernel/nullfs.ko: Unsupported file type
 
 Nicola
From naliyev at ultel.az  Sun Dec 28 21:41:55 2008
From: naliyev at ultel.az (Nadir M. Aliyev)
Date: Mon Dec 29 04:17:25 2008
Subject: amd64 bug :(
Message-ID: <20081229054150.B71E8444DF9@mail.ultel.net>

Hi. I want to talk you about bugs wth ciss (Smart Array p400) 

I have server HP Proliant DL380 G5 Storage Rack server. 

With 2x Intel Xeon 2.5 Ghz, 10 GB of RAM, 6 SAS disk [ 5 (RAID5) + 1 (ONLINE
SPARE) ] and Smart Array P400 with 256 mb memory. 

 

i installed 64 bit version and I have a great problems:

 

 

i can install FreeBSD amd64 in normal mode But i can not load/install system
ACPI or safe mode.

 

Sometimes its fault issues while server working ( when I plug/unplug hotswap
drive or usb disk drive ) and then rebooting.

 

This is error code:

----------------------------------------------------------------------------
---------------------

ciss0: <HP Smart Array P400> port0x4000 mem
0xfde00000-0xfdefffff,0xfddf0000-0xfddf0fff irq 10 ad device 0.0 on pci6

ciss can't allocate interrupt

 

Fatal trap 12: page fault while in kernel mode

cpuid = 0; apic id        = 00

fault virtual address    = 0x30

fault code                    = supervisor read data, page not present

instruction pointer:     = 0x8:0xffffffff80487e2f

stack pointer               = 0x10:0xffffffff80af3850

frame pointer              = 0x10:0xffffffff8098bd50

code segment             = base 0x0, limit 0xfffff, type 0x1b

                                   = DPL 0, pres 1, long 1, def32 0, gran 1

processor eflags         = resume, IOPL = 0

current process           = 0 (swaper)

trap number                = 12

panic: page fault

----------------------------------------------------------------------------
---------------------

This bug issues with Freebsd 64bit 7.1 rc2 too. 

 

I tried 32 bit freebsd 7.0 on my new server. 32 bit works perfectly!!! But I
don't want use 32 bit. I have 10GB of RAM. more than 4 gb.

 

Please help me how can i fix this problem. Anybody can help?

Great Thanks

 

 

 

* * * 
Nadir Aliyev  
System and Unix Administrator
ULTEL LTD. Internet & Information Technologies Department 
14 M.Mekhti-zade. Baku, Azerbaijan AZ1023 

Work:     +994(12) 4967199
Mobile:    +994(55) 7012310
www:        <http://www.ultel.az> http://www.ultel.az 

 

-------------- next part --------------
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-RELEASE #0: Fri Dec 26 16:35:40 AZT 2008
    nadir@billing.ultel.net:/usr/src/sys/amd64/compile/GENERIC_CUSTOMCISS_26122008_NAD
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz (2500.02-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x1067a  Stepping = 10
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x40ce3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,<b19>,<b26>>
  AMD Features=0x20000800<SYSCALL,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 4
usable memory = 10723770368 (10226 MB)
avail memory  = 10373492736 (9892 MB)
ACPI APIC Table: <HP     ProLiant>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <HP ProLiant> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0: <ACPI CPU> on acpi0
ACPI Error (psargs-0459): [CS03] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0626): Method parse/execution failed [\\_PR_.CPU0._CST] (Node 0xffffff000126a5c0), AE_NOT_FOUND
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est2 attach returned 6
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est3 attach returned 6
p4tcc3: <CPU Frequency Thermal Control> on cpu3
cpu4: <ACPI CPU> on acpi0
est4: <Enhanced SpeedStep Frequency Control> on cpu4
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est4 attach returned 6
p4tcc4: <CPU Frequency Thermal Control> on cpu4
cpu5: <ACPI CPU> on acpi0
est5: <Enhanced SpeedStep Frequency Control> on cpu5
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est5 attach returned 6
p4tcc5: <CPU Frequency Thermal Control> on cpu5
cpu6: <ACPI CPU> on acpi0
est6: <Enhanced SpeedStep Frequency Control> on cpu6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est6 attach returned 6
p4tcc6: <CPU Frequency Thermal Control> on cpu6
cpu7: <ACPI CPU> on acpi0
est7: <Enhanced SpeedStep Frequency Control> on cpu7
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4722472206004722
device_attach: est7 attach returned 6
p4tcc7: <CPU Frequency Thermal Control> on cpu7
pcib0: <ACPI Host-PCI bridge> on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci9: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci9
pci10: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 0.0 on pci10
pci11: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 1.0 on pci10
pci14: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 2.0 on pci10
pci17: <ACPI PCI bus> on pcib5
pcib6: <PCI-PCI bridge> at device 0.3 on pci9
pci18: <PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci6: <ACPI PCI bus> on pcib7
ciss0: <HP Smart Array P400> port 0x4000-0x40ff mem 0xfde00000-0xfdefffff,0xfddf0000-0xfddf0fff irq 18 at device 0.0 on pci6
ciss0: [ITHREAD]
pcib8: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci19: <ACPI PCI bus> on pcib8
pcib9: <PCI-PCI bridge> at device 5.0 on pci0
pci22: <PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci23: <ACPI PCI bus> on pcib10
pcib11: <PCI-PCI bridge> at device 7.0 on pci0
pci26: <PCI bus> on pcib11
pcib12: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib12
pcib13: <PCI-PCI bridge> at device 0.0 on pci2
pci3: <PCI bus> on pcib13
bce0: <Broadcom NetXtreme II BCM5708 1000Base-T (B2)> mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci3
miibus0: <MII bus> on bce0
brgphy0: <BCM5708C 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce0: Ethernet address: 00:21:5a:f3:36:20
bce0: [ITHREAD]
bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x01090605); Flags( MFW MSI )
pcib14: <ACPI PCI-PCI bridge> at device 28.1 on pci0
pci4: <ACPI PCI bus> on pcib14
pcib15: <PCI-PCI bridge> at device 0.0 on pci4
pci5: <PCI bus> on pcib15
bce1: <Broadcom NetXtreme II BCM5708 1000Base-T (B2)> mem 0xfa000000-0xfbffffff irq 17 at device 0.0 on pci5
miibus1: <MII bus> on bce1
brgphy1: <BCM5708C 10/100/1000baseTX PHY> PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce1: Ethernet address: 00:21:5a:f3:36:1e
bce1: [ITHREAD]
bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x01090605); Flags( MFW MSI )
uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x1000-0x101f irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <Intel 631XESB/632XESB/3100 USB controller USB-1> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 631XESB/632XESB/3100 USB controller USB-2> port 0x1020-0x103f irq 17 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <Intel 631XESB/632XESB/3100 USB controller USB-2> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 631XESB/632XESB/3100 USB controller USB-3> port 0x1040-0x105f irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: <Intel 631XESB/632XESB/3100 USB controller USB-3> on uhci2
usb2: USB revision 1.0
uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
uhci3: <Intel 631XESB/632XESB/3100 USB controller USB-4> port 0x1060-0x107f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb3: <Intel 631XESB/632XESB/3100 USB controller USB-4> on uhci3
usb3: USB revision 1.0
uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ehci0: <Intel 63XXESB USB 2.0 controller> mem 0xf7df0000-0xf7df03ff irq 16 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb4: waiting for BIOS to give up control
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <Intel 63XXESB USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
uhub4: 8 ports with 8 removable, self powered
pcib16: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib16
vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem 0xd8000000-0xdfffffff,0xf7ff0000-0xf7ffffff irq 23 at device 3.0 on pci1
pci1: <base peripheral> at device 4.0 (no driver attached)
pci1: <base peripheral> at device 4.2 (no driver attached)
uhci4: <UHCI (generic) USB controller> port 0x3800-0x381f irq 22 at device 4.4 on pci1
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub5: <(0x103c) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
uhub5: 2 ports with 2 removable, self powered
pci1: <serial bus> at device 4.6 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 63XXESB2 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f irq 17 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <Standard PC COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcafff,0xe6000-0xe7fff on isa0
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio1: [FILTER]
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd0: <HP Virtual Keyboard, class 0/0, rev 1.10/0.02, addr 2> on uhub5
kbd2 at ukbd0
ums0: <HP Virtual Keyboard, class 0/0, rev 1.10/0.02, addr 2> on uhub5
ums0: 3 buttons.
uhub6: <HP Virtual Hub, class 9/0, rev 1.10/0.01, addr 3> on uhub5
uhub6: 7 ports with 7 removable, self powered
Timecounters tick every 1.000 msec
acd0: DVDR <TEAC DV-W28E-RW/G.B2> at ata0-master UDMA33
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #4 Launched!
da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 5  VOLUME OK> Fixed Direct Access SCSI-5 device 
da0: 135.168MB/s transfers
da0: 559928MB (1146733360 512 byte sectors: 255H 63S/T 65535C)
Trying to mount root from ufs:/dev/da0s1a
bce0: link state changed to UP
From bugmaster at FreeBSD.org  Mon Dec 29 03:06:51 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Dec 29 04:17:40 2008
Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org
Message-ID: <200812291106.mBTB6o5w024361@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o amd64/129889 amd64      [boot] The booting process stops at the line mounting 
o amd64/129721 amd64      [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R
o amd64/129667 amd64      [ata] Elitegroup A780GM-A IDE controller not recognize
o amd64/129488 amd64      [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: 
o amd64/129426 amd64      [panic] FreeBSD 7.0 crash after subdiskXX: detached
o amd64/129315 amd64      [boot] amd64 motherboard: Intel DG965WH motherboard co
f amd64/128978 amd64      [install] FreeBSD 6.3 64-bit  panics at boot time duri
o amd64/128810 amd64      AMD 64 port installation
o amd64/128765 amd64      [install] Install CD loads to Install choices but stop
o amd64/128686 amd64      [ata] can't detect SATA Disk on 8.0-Current with NF550
o amd64/128524 amd64      No geom documentation for loading gjournal
o amd64/128263 amd64      [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a
o amd64/128259 amd64      csh(1): "`" crashes csh
o amd64/128236 amd64      portsdb -Uu Indexing error
f kern/128102  amd64      AsusRock 939N68PV-GLAN not recognized
o amd64/127787 amd64      [lor] 3 lock LOR in recent CURRENT
o amd64/127640 amd64      GCC will not build shared libraries with -fprofile-gen
o amd64/127492 amd64      [zfs] System hang on ZFS input-output
o amd64/127484 amd64      [timecounters] Drift problem with FreeBSD 7.0 and 7.1 
o amd64/127451 amd64      [scheduler] incorrect load on quad core
o amd64/127397 amd64      [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI
s amd64/127276 amd64      ldd(1) invokes linux yes
o amd64/127129 amd64      mdconfig(8) is core dumping with Segmentation Fault 11
f amd64/125943 amd64      Serial Consoles do not work on amd64 freebsd
o amd64/125873 amd64      [smbd] [panic] Repeated kernel panics, trap 12 page fa
o amd64/125002 amd64      [install] amd64, SATA hard disks not detected
o amd64/124432 amd64      [panic] 7.0-STABLE panic: invalbuf: dirty bufs
o amd64/124134 amd64      [kernel] The kernel doesn't follow the calling convent
o amd64/123562 amd64      [install] FreeBSD amd64 not installs
o amd64/123520 amd64      [ahd] unable to boot from net while using ahd
o amd64/123456 amd64      fstat(1): /usr/bin/fstat shows error messages and hang
f amd64/123275 amd64      [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re
o kern/122782  amd64      [modules] accf_http.ko kernel module is not loadable
o amd64/122695 amd64      [cpufreq] Lack of cpufreq control using amd64 eith cor
o amd64/122624 amd64      unusable minimal installation of FreeBSD-7.0
o amd64/122549 amd64      7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial 
o amd64/122468 amd64      Compile problems after upgrading to 7.0
o amd64/122174 amd64      [panic] 7.0 no longer includes "device atpic" so fails
o amd64/121590 amd64      [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet
o amd64/121439 amd64      [boot] Installation of FreeBSD 7.0 fails: ACPI problem
o amd64/120202 amd64      [amd64] [patch] [panic] kernel panic at start_all_aps,
o amd64/119936 amd64      [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis
o amd64/119591 amd64      [amd64] [patch] time_t on 64-bit architecture
o amd64/117418 amd64      [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh
o amd64/117316 amd64      [acpi] ACPI lockups on SuperMicro motherboard
o amd64/117296 amd64      [ata] I don`t see second SATA IDE on VIA VT8237A
a amd64/117186 amd64      [modules] kldload Unsupported file type on STABLE amd6
s amd64/116689 amd64      [request] support for MSI K9MM-V
f amd64/116670 amd64      [ata] onboard SATA RAID1 controllers not supported for
o amd64/116620 amd64      [hang] ifconfig spins when creating carp(4) device on 
o amd64/116322 amd64      [panic] At start fsck on current, the system panics
o amd64/116159 amd64      [panic] Panic while debugging on CURRENT
s amd64/115815 amd64      [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp
o amd64/115581 amd64      [Makefile] [patch] -mfancy-math-387 has no effect
o amd64/115194 amd64      LCD screen remains blank after Dell XPS M1210 lid is c
o amd64/114270 amd64      [cpufreq] cpufreq doesnt work when compiled in to kern
o amd64/114111 amd64      [nfs] System crashes while writing on NFS-mounted shar
f amd64/113021 amd64      [re] ASUS M2A-VM onboard NIC does not work
o amd64/112222 amd64      [libc] 32-bit libc incorrectly converts some FP number
f amd64/111992 amd64      [boot] BTX failed - HP Laptop dv2315nr
o amd64/110655 amd64      [threads] 32 bit threaded applications crash on amd64 
o amd64/110599 amd64      [geli] geli attach to gmirror device hangs and cannot 
s amd64/108861 amd64      [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work
o amd64/106186 amd64      [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p
f amd64/105629 amd64      [re] TrendNet TEG-BUSR 10/100/1000 disables itself on 
f amd64/105531 amd64      [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does
f amd64/105514 amd64      [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv
o amd64/102716 amd64      ex with no argument in an xterm gets SIGSEGV
o amd64/97337  amd64      [dri] xorg reboots system if dri module is enabled
o amd64/95888  amd64      [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP 
f amd64/94989  amd64      [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64)
o amd64/94677  amd64      [panic] panic in amd64 install at non-root user creati
o amd64/93961  amd64      [busdma] Problem in bounce buffer handling in sys/amd6
o amd64/92337  amd64      [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff
f amd64/91492  amd64      [boot] BTX halted
o amd64/91405  amd64      [asr] [panic] Kernel panic caused by asr on 6.0-amd64 
o amd64/89501  amd64      [install] System crashes on install using ftp on local
o amd64/88790  amd64      [panic] kernel panic on first boot (after the FreeBSD 
o amd64/88568  amd64      [panic] 6.0-RELEASE install cd does not boot with usb 
o amd64/87689  amd64      [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE
o amd64/87316  amd64      [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6
o amd64/87305  amd64      [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in
f amd64/87258  amd64      [smp] [boot] cannot boot with SMP and Areca ARC-1160 r
f amd64/86080  amd64      [radeon] [hang] radeon DRI causes system hang on amd64
s amd64/85273  amd64      [install] FreeBSD (NetBSD or OpenBSD) not install on l
o amd64/78406  amd64      [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys
o amd64/76136  amd64      [hang] system halts before reboot
o amd64/74747  amd64      [panic] System panic on shutdown when process will not
o amd64/73322  amd64      [msdosfs] [hang] unarchiving /etc to msdosfs locks up 

89 problems total.

From tinderbox at freebsd.org  Mon Dec 29 16:49:05 2008
From: tinderbox at freebsd.org (FreeBSD Tinderbox)
Date: Mon Dec 29 16:50:00 2008
Subject: [head tinderbox] failure on amd64/amd64
Message-ID: <20081229164901.59E387302F@freebsd-current.sentex.ca>

TB --- 2008-12-29 14:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2008-12-29 14:40:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2008-12-29 14:40:00 - cleaning the object tree
TB --- 2008-12-29 14:40:52 - cvsupping the source tree
TB --- 2008-12-29 14:40:52 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile
TB --- 2008-12-29 14:41:00 - building world
TB --- 2008-12-29 14:41:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-29 14:41:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-29 14:41:00 - TARGET=amd64
TB --- 2008-12-29 14:41:00 - TARGET_ARCH=amd64
TB --- 2008-12-29 14:41:00 - TZ=UTC
TB --- 2008-12-29 14:41:00 - __MAKE_CONF=/dev/null
TB --- 2008-12-29 14:41:00 - cd /src
TB --- 2008-12-29 14:41:00 - /usr/bin/make -B buildworld
>>> World build started on Mon Dec 29 14:41:02 UTC 2008
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
>>> stage 5.1: building 32 bit shim libraries
>>> World build completed on Mon Dec 29 16:36:16 UTC 2008
TB --- 2008-12-29 16:36:16 - generating LINT kernel config
TB --- 2008-12-29 16:36:16 - cd /src/sys/amd64/conf
TB --- 2008-12-29 16:36:16 - /usr/bin/make -B LINT
TB --- 2008-12-29 16:36:16 - building LINT kernel
TB --- 2008-12-29 16:36:16 - MAKEOBJDIRPREFIX=/obj
TB --- 2008-12-29 16:36:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2008-12-29 16:36:16 - TARGET=amd64
TB --- 2008-12-29 16:36:16 - TARGET_ARCH=amd64
TB --- 2008-12-29 16:36:16 - TZ=UTC
TB --- 2008-12-29 16:36:16 - __MAKE_CONF=/dev/null
TB --- 2008-12-29 16:36:16 - cd /src
TB --- 2008-12-29 16:36:16 - /usr/bin/make -B buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Mon Dec 29 16:36:17 UTC 2008
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/kern_time.c
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/kern_timeout.c
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/kern_umtx.c
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/kern_uuid.c
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone  -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/kern_xxx.c
cc1: warnings being treated as errors
/src/sys/kern/kern_xxx.c: In function 'osethostname':
/src/sys/kern/kern_xxx.c:86: warning: unused variable 'error'
*** Error code 1

Stop in /obj/amd64/src/sys/LINT.
*** Error code 1

Stop in /src.
*** Error code 1

Stop in /src.
TB --- 2008-12-29 16:49:01 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2008-12-29 16:49:01 - ERROR: failed to build lint kernel
TB --- 2008-12-29 16:49:01 - 6152.52 user 625.55 system 7740.74 real


http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full