From tinderbox at freebsd.org Thu Jan 1 05:20:20 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jan 1 05:20:27 2009 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20090101052017.E15197302F@freebsd-current.sentex.ca> TB --- 2009-01-01 03:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-01 03:00:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-01-01 03:00:00 - cleaning the object tree TB --- 2009-01-01 03:00:51 - cvsupping the source tree TB --- 2009-01-01 03:00:51 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-01-01 03:05:49 - building world TB --- 2009-01-01 03:05:49 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-01 03:05:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-01 03:05:49 - TARGET=amd64 TB --- 2009-01-01 03:05:49 - TARGET_ARCH=amd64 TB --- 2009-01-01 03:05:49 - TZ=UTC TB --- 2009-01-01 03:05:49 - __MAKE_CONF=/dev/null TB --- 2009-01-01 03:05:49 - cd /src TB --- 2009-01-01 03:05:49 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 1 03:05:50 UTC 2009 >>> 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 Thu Jan 1 05:02:36 UTC 2009 TB --- 2009-01-01 05:02:36 - generating LINT kernel config TB --- 2009-01-01 05:02:36 - cd /src/sys/amd64/conf TB --- 2009-01-01 05:02:36 - /usr/bin/make -B LINT TB --- 2009-01-01 05:02:37 - building LINT kernel TB --- 2009-01-01 05:02:37 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-01 05:02:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-01 05:02:37 - TARGET=amd64 TB --- 2009-01-01 05:02:37 - TARGET_ARCH=amd64 TB --- 2009-01-01 05:02:37 - TZ=UTC TB --- 2009-01-01 05:02:37 - __MAKE_CONF=/dev/null TB --- 2009-01-01 05:02:37 - cd /src TB --- 2009-01-01 05:02:37 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 1 05:02:37 UTC 2009 >>> 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 [...] kern_mib.o(.bss+0x2b8): multiple definition of `elf64_fallback_brand' imgact_elf.o(.data+0x0): first defined here elf_machdep.o(.bss+0x0): multiple definition of `elf64_fallback_brand' imgact_elf.o(.data+0x0): first defined here imgact_elf32.o(.data+0x0): multiple definition of `elf32_fallback_brand' ia32_sysvec.o(.bss+0x0): first defined here linux32_sysvec.o(.bss+0x0): multiple definition of `elf32_fallback_brand' ia32_sysvec.o(.bss+0x0): first defined here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-01 05:20:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-01 05:20:17 - ERROR: failed to build lint kernel TB --- 2009-01-01 05:20:17 - 6447.54 user 641.41 system 8417.14 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From tinderbox at freebsd.org Thu Jan 1 12:54:35 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jan 1 12:54:52 2009 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20090101125432.7E8DB7302F@freebsd-current.sentex.ca> TB --- 2009-01-01 10:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-01-01 10:40:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-01-01 10:40:01 - cleaning the object tree TB --- 2009-01-01 10:40:41 - cvsupping the source tree TB --- 2009-01-01 10:40:41 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-01-01 10:40:48 - building world TB --- 2009-01-01 10:40:48 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-01 10:40:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-01 10:40:48 - TARGET=amd64 TB --- 2009-01-01 10:40:48 - TARGET_ARCH=amd64 TB --- 2009-01-01 10:40:48 - TZ=UTC TB --- 2009-01-01 10:40:48 - __MAKE_CONF=/dev/null TB --- 2009-01-01 10:40:48 - cd /src TB --- 2009-01-01 10:40:48 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 1 10:40:51 UTC 2009 >>> 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 Thu Jan 1 12:36:26 UTC 2009 TB --- 2009-01-01 12:36:26 - generating LINT kernel config TB --- 2009-01-01 12:36:26 - cd /src/sys/amd64/conf TB --- 2009-01-01 12:36:26 - /usr/bin/make -B LINT TB --- 2009-01-01 12:36:26 - building LINT kernel TB --- 2009-01-01 12:36:26 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-01 12:36:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-01 12:36:26 - TARGET=amd64 TB --- 2009-01-01 12:36:26 - TARGET_ARCH=amd64 TB --- 2009-01-01 12:36:26 - TZ=UTC TB --- 2009-01-01 12:36:26 - __MAKE_CONF=/dev/null TB --- 2009-01-01 12:36:26 - cd /src TB --- 2009-01-01 12:36:26 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 1 12:36:26 UTC 2009 >>> 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 [...] kern_mib.o(.bss+0x2b8): multiple definition of `elf64_fallback_brand' imgact_elf.o(.data+0x0): first defined here elf_machdep.o(.bss+0x0): multiple definition of `elf64_fallback_brand' imgact_elf.o(.data+0x0): first defined here imgact_elf32.o(.data+0x0): multiple definition of `elf32_fallback_brand' ia32_sysvec.o(.bss+0x0): first defined here linux32_sysvec.o(.bss+0x0): multiple definition of `elf32_fallback_brand' ia32_sysvec.o(.bss+0x0): first defined here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-01 12:54:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-01 12:54:32 - ERROR: failed to build lint kernel TB --- 2009-01-01 12:54:32 - 6442.43 user 635.49 system 8071.36 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From linimon at FreeBSD.org Fri Jan 2 00:29:33 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Jan 2 01:04:48 2009 Subject: amd64/130103: [hang] 7.1-RC X -> systemcrash Message-ID: <200901020029.n020TWcu042578@freefall.freebsd.org> Old Synopsis: 7.1-RC X -> systemcrash New Synopsis: [hang] 7.1-RC X -> systemcrash Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 2 00:28:44 UTC 2009 Responsible-Changed-Why: Reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=130103 From oliver.pntr at gmail.com Fri Jan 2 16:20:04 2009 From: oliver.pntr at gmail.com (Oliver Pinter) Date: Fri Jan 2 16:20:12 2009 Subject: misc/130103: 7.1-RC X -> systemcrash Message-ID: <200901021620.n02GK3Po076163@freefall.freebsd.org> The following reply was made to PR amd64/130103; it has been noted by GNATS. From: "Oliver Pinter" To: "Benjamin Stuppin" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: misc/130103: 7.1-RC X -> systemcrash Date: Fri, 2 Jan 2009 16:46:01 +0100 Hi, I have this system: ASUS P5Q-E Intel Q9300 Sapphire RHD3450 4GB RAM I use FreeBSD 7.1RC2 from csup (20081223) and from xorg-video-driver-ati from ports, with this driver worked fine, without system crash, can you the ati driver use? On 1/2/09, Benjamin Stuppin wrote: > >>Number: 130103 >>Category: misc >>Synopsis: 7.1-RC X -> systemcrash >>Confidential: no >>Severity: non-critical >>Priority: low >>Responsible: freebsd-bugs >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Thu Jan 01 23:30:01 UTC 2009 >>Closed-Date: >>Last-Modified: >>Originator: Benjamin Stuppin >>Release: 7.1-RC2 amd64 >>Organization: >>Environment: > FreeBSD rechner.local.net 7.1-RC2 FreeBSD 7.1-RC2 #0: Tue Dec 23 11:42:13 > UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > >>Description: > Hi, > when i install FreeBSD 7.1-RC1/2 and install X11 my system hangs up when i > startx -> logout -> startx > it also hung up after installing drm for radeonhd -> startx -> mplayer > -> fullscreen -> normal mode > > The System freezes so i can't do anything (lack another pc to test if only x > runs but sometime i also saw a kernel panic message when i was on terminal 1 > during a crash). > > I tryed it doing a installation from 7.1-RC DVD, all software installed from > DVD. (Full install X-Devel) > Also tryed minimal installation -> freebsd-update -> ports from cvs -> build > everything from source. > Also tryed radeon/radeonhd/ati drivers for my r5xx based ati card. > > 7.0 runs fine > > System: > Intel Core2quad Q6700 > Asus P5K SP/EPU > Ati Radeon x1300 (pcie) > > dmesg: > > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 4 > usable memory = 4282462208 (4084 MB) > avail memory = 4121108480 (3930 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > hptrr: HPT RocketRAID controller driver v1.1 (Jan 1 2009 21:10:24) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > cpu0: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 7F, > should be 76 [20070320] > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est0 attach returned 6 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est1 attach returned 6 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est2 attach returned 6 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est3 attach returned 6 > p4tcc3: on cpu3 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xc000-0xc0ff mem > 0xd0000000-0xdfffffff,0xfe9e0000-0xfe9effff irq 16 at device 0.0 on pci1 > vgapci1: mem 0xfe9f0000-0xfe9fffff at device 0.1 on > pci1 > uhci0: port 0xb800-0xb81f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xb880-0xb89f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xbc00-0xbc1f irq 18 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfe8ffc00-0xfe8fffff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pcm0: mem > 0xfe8f8000-0xfe8fbfff irq 22 at device 27.0 on pci0 > pcm0: [ITHREAD] > pcib2: irq 17 at device 28.0 on pci0 > pci3: on pcib2 > pcib3: irq 17 at device 28.4 on pci0 > pci2: on pcib3 > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem > 0xfeaffc00-0xfeafffff irq 16 at device 0.0 on pci2 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > uhci3: port 0xb080-0xb09f irq 23 at device > 29.0 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb4: on uhci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > uhci4: port 0xb400-0xb41f irq 19 at device > 29.1 on pci0 > uhci4: [GIANT-LOCKED] > uhci4: [ITHREAD] > usb5: on uhci4 > usb5: USB revision 1.0 > uhub5: on usb5 > uhub5: 2 ports with 2 removable, self powered > uhci5: port 0xb480-0xb49f irq 18 at device > 29.2 on pci0 > uhci5: [GIANT-LOCKED] > uhci5: [ITHREAD] > usb6: on uhci5 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > ehci1: mem 0xfe8ff800-0xfe8ffbff irq 23 > at device 29.7 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb7: EHCI version 1.0 > usb7: companion controllers, 2 ports each: usb4 usb5 usb6 > usb7: on ehci1 > usb7: USB revision 2.0 > uhub7: on usb7 > uhub7: 6 ports with 6 removable, self powered > uhub7: port 6, set config at addr 2 failed > uhub7: device problem (INVAL), disabling port 6 > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xfebffc00-0xfebffc7f irq 16 at device 0.0 on pci4 > miibus0: on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:10:5a:69:26:6b > xl0: [ITHREAD] > bktr0: mem 0xfdffe000-0xfdffefff irq 17 at device 1.0 on > pci4 > bktr0: [GIANT-LOCKED] > bktr0: [ITHREAD] > bktr0: Hauppauge Model 61344 D221 > bktr0: Detected a MSP3415D-A2 at 0x80 > bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, > remote control. > pci4: at device 1.1 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f,0x9400-0x940f > irq 22 at device 31.2 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci2: port > 0xb000-0xb007,0xac00-0xac03,0xa880-0xa887,0xa800-0xa803,0xa480-0xa48f,0xa400-0xa40f > irq 22 at device 31.5 on pci0 > atapci2: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > acpi_button0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > ppc0: cannot reserve I/O port range > sc0: 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 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on > uhub2 > ums0: 16 buttons and Z dir. > uhid0: on > uhub2 > umass0: on uhub5 > Timecounters tick every 1.000 msec > hptrr: no controller detected. > ad8: 476940MB at ata4-master SATA300 > ad10: 238475MB at ata5-master SATA150 > GEOM_LABEL: Label for provider ad10s3 is ntfs/System. > acd0: DVDR at ata6-master SATA150 > ad14: 953869MB at ata7-master SATA300 > pcm0: > pcm0: > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da1 at umass-sim0 bus 0 target 0 lun 1 > da1: Removable Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present > da2 at umass-sim0 bus 0 target 0 lun 2 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 3 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > GEOM_LABEL: Label for provider acd0 is iso9660/CANOSCAN. > Trying to mount root from ufs:/dev/ad8s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > WARNING: /usr was not properly dismounted > WARNING: /var was not properly dismounted > WARNING: /lager was not properly dismounted > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > pid 749 (hald-addon-mouse-sy), uid 0: exited on signal 11 (core dumped) > 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-p7 #1: Thu Jan 1 21:10:29 CET 2009 > root@rechner.local.net:/usr/obj/usr/src/sys/VEGA > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2666.77-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 4 > usable memory = 4282462208 (4084 MB) > avail memory = 4121108480 (3930 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > hptrr: HPT RocketRAID controller driver v1.1 (Jan 1 2009 21:10:24) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > cpu0: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 7F, > should be 76 [20070320] > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est0 attach returned 6 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est1 attach returned 6 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est2 attach returned 6 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr a280a2806000a28 > device_attach: est3 attach returned 6 > p4tcc3: on cpu3 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xc000-0xc0ff mem > 0xd0000000-0xdfffffff,0xfe9e0000-0xfe9effff irq 16 at device 0.0 on pci1 > vgapci1: mem 0xfe9f0000-0xfe9fffff at device 0.1 on > pci1 > uhci0: port 0xb800-0xb81f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xb880-0xb89f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xbc00-0xbc1f irq 18 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfe8ffc00-0xfe8fffff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pcm0: mem > 0xfe8f8000-0xfe8fbfff irq 22 at device 27.0 on pci0 > pcm0: [ITHREAD] > pcib2: irq 17 at device 28.0 on pci0 > pci3: on pcib2 > pcib3: irq 17 at device 28.4 on pci0 > pci2: on pcib3 > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem > 0xfeaffc00-0xfeafffff irq 16 at device 0.0 on pci2 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > uhci3: port 0xb080-0xb09f irq 23 at device > 29.0 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb4: on uhci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > uhci4: port 0xb400-0xb41f irq 19 at device > 29.1 on pci0 > uhci4: [GIANT-LOCKED] > uhci4: [ITHREAD] > usb5: on uhci4 > usb5: USB revision 1.0 > uhub5: on usb5 > uhub5: 2 ports with 2 removable, self powered > uhci5: port 0xb480-0xb49f irq 18 at device > 29.2 on pci0 > uhci5: [GIANT-LOCKED] > uhci5: [ITHREAD] > usb6: on uhci5 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > ehci1: mem 0xfe8ff800-0xfe8ffbff irq 23 > at device 29.7 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb7: EHCI version 1.0 > usb7: companion controllers, 2 ports each: usb4 usb5 usb6 > usb7: on ehci1 > usb7: USB revision 2.0 > uhub7: on usb7 > uhub7: 6 ports with 6 removable, self powered > uhub7: port 6, set config at addr 2 failed > uhub7: device problem (INVAL), disabling port 6 > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xfebffc00-0xfebffc7f irq 16 at device 0.0 on pci4 > miibus0: on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:10:5a:69:26:6b > xl0: [ITHREAD] > bktr0: mem 0xfdffe000-0xfdffefff irq 17 at device 1.0 on > pci4 > bktr0: [GIANT-LOCKED] > bktr0: [ITHREAD] > bktr0: Hauppauge Model 61344 D221 > bktr0: Detected a MSP3415D-A2 at 0x80 > bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, > remote control. > pci4: at device 1.1 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f,0x9400-0x940f > irq 22 at device 31.2 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci2: port > 0xb000-0xb007,0xac00-0xac03,0xa880-0xa887,0xa800-0xa803,0xa480-0xa48f,0xa400-0xa40f > irq 22 at device 31.5 on pci0 > atapci2: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > acpi_button0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > ppc0: cannot reserve I/O port range > sc0: 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 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on > uhub2 > ums0: 16 buttons and Z dir. > uhid0: on > uhub2 > umass0: on uhub5 > Timecounters tick every 1.000 msec > hptrr: no controller detected. > ad8: 476940MB at ata4-master SATA300 > ad10: 238475MB at ata5-master SATA150 > GEOM_LABEL: Label for provider ad10s3 is ntfs/System. > acd0: DVDR at ata6-master SATA150 > ad14: 953869MB at ata7-master SATA300 > pcm0: > pcm0: > SMP: AP CPU #3 Launched! > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da1 at umass-sim0 bus 0 target 0 lun 1 > da1: Removable Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present > da2 at umass-sim0 bus 0 target 0 lun 2 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 3 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > Trying to mount root from ufs:/dev/ad8s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > WARNING: /usr was not properly dismounted > WARNING: /var was not properly dismounted > WARNING: /lager was not properly dismounted > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > KLD radeon.ko: depends on drm - not available > kldload: Unsupported file type > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > warning: KLD '/boot/kernel/drm.ko' is newer than the linker.hints file > link_elf_obj: symbol DRM_MEM_DRIVER undefined > kldload: Unsupported file type > link_elf_obj: symbol DRM_MEM_DRIVER undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > link_elf_obj: symbol devfs_get_cdevpriv undefined > kldload: Unsupported file type > 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-RC2 #0: Tue Dec 23 11:42:13 UTC 2008 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2666.78-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 4 > usable memory = 4276789248 (4078 MB) > avail memory = 4115329024 (3924 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xc000-0xc0ff mem > 0xd0000000-0xdfffffff,0xfe9e0000-0xfe9effff irq 16 at device 0.0 on pci1 > vgapci1: mem 0xfe9f0000-0xfe9fffff at device 0.1 on > pci1 > uhci0: port 0xb800-0xb81f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xb880-0xb89f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xbc00-0xbc1f irq 18 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfe8ffc00-0xfe8fffff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pci0: at device 27.0 (no driver attached) > pcib2: irq 17 at device 28.0 on pci0 > pci3: on pcib2 > pcib3: irq 17 at device 28.4 on pci0 > pci2: on pcib3 > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem > 0xfeaffc00-0xfeafffff irq 16 at device 0.0 on pci2 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > uhci3: port 0xb080-0xb09f irq 23 at device > 29.0 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb4: on uhci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > uhci4: port 0xb400-0xb41f irq 19 at device > 29.1 on pci0 > uhci4: [GIANT-LOCKED] > uhci4: [ITHREAD] > usb5: on uhci4 > usb5: USB revision 1.0 > uhub5: on usb5 > uhub5: 2 ports with 2 removable, self powered > uhci5: port 0xb480-0xb49f irq 18 at device > 29.2 on pci0 > uhci5: [GIANT-LOCKED] > uhci5: [ITHREAD] > usb6: on uhci5 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > ehci1: mem 0xfe8ff800-0xfe8ffbff irq 23 > at device 29.7 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb7: EHCI version 1.0 > usb7: companion controllers, 2 ports each: usb4 usb5 usb6 > usb7: on ehci1 > usb7: USB revision 2.0 > uhub7: on usb7 > uhub7: 6 ports with 6 removable, self powered > uhub7: port 6, set config at addr 2 failed > uhub7: device problem (INVAL), disabling port 6 > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xfebffc00-0xfebffc7f irq 16 at device 0.0 on pci4 > miibus0: on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:10:5a:69:26:6b > xl0: [ITHREAD] > pci4: at device 1.0 (no driver attached) > pci4: at device 1.1 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f,0x9400-0x940f > irq 22 at device 31.2 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci2: port > 0xb000-0xb007,0xac00-0xac03,0xa880-0xa887,0xa800-0xa803,0xa480-0xa48f,0xa400-0xa40f > irq 22 at device 31.5 on pci0 > atapci2: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > acpi_button0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > cpu0: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 7F, > should be 76 [20070320] > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > p4tcc3: on cpu3 > ppc0: cannot reserve I/O port range > sc0: 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 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on > uhub2 > ums0: 16 buttons and Z dir. > uhid0: on > uhub2 > umass0: on uhub5 > Timecounters tick every 1.000 msec > md0: Preloaded image 4194304 bytes at 0xffffffff80c6fd98 > ad8: 476940MB at ata4-master SATA300 > ad10: 238475MB at ata5-master SATA150 > GEOM_LABEL: Label for provider ad10s3 is ntfs/System. > acd0: DVDR at ata6-master SATA150 > ad14: 953869MB at ata7-master SATA300 > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install. > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da1 at umass-sim0 bus 0 target 0 lun 1 > da1: Removable Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present > da2 at umass-sim0 bus 0 target 0 lun 2 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 3 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > Trying to mount root from ufs:/dev/md0 > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max > S6y0n csiencgo nddiss)k sf,o rv nsoydsetse mr epmraoicneisnsg .`.s.ynce9r ' > to stop...9 4 0 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 7.1-RC2 #0: Tue Dec 23 11:42:13 UTC 2008 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2666.77-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 4 > usable memory = 4280983552 (4082 MB) > avail memory = 4119531520 (3928 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xc000-0xc0ff mem > 0xd0000000-0xdfffffff,0xfe9e0000-0xfe9effff irq 16 at device 0.0 on pci1 > vgapci1: mem 0xfe9f0000-0xfe9fffff at device 0.1 on > pci1 > uhci0: port 0xb800-0xb81f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xb880-0xb89f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xbc00-0xbc1f irq 18 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfe8ffc00-0xfe8fffff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > pci0: at device 27.0 (no driver attached) > pcib2: irq 17 at device 28.0 on pci0 > pci3: on pcib2 > pcib3: irq 17 at device 28.4 on pci0 > pci2: on pcib3 > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem > 0xfeaffc00-0xfeafffff irq 16 at device 0.0 on pci2 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > uhci3: port 0xb080-0xb09f irq 23 at device > 29.0 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb4: on uhci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > uhci4: port 0xb400-0xb41f irq 19 at device > 29.1 on pci0 > uhci4: [GIANT-LOCKED] > uhci4: [ITHREAD] > usb5: on uhci4 > usb5: USB revision 1.0 > uhub5: on usb5 > uhub5: 2 ports with 2 removable, self powered > uhci5: port 0xb480-0xb49f irq 18 at device > 29.2 on pci0 > uhci5: [GIANT-LOCKED] > uhci5: [ITHREAD] > usb6: on uhci5 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > ehci1: mem 0xfe8ff800-0xfe8ffbff irq 23 > at device 29.7 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb7: EHCI version 1.0 > usb7: companion controllers, 2 ports each: usb4 usb5 usb6 > usb7: on ehci1 > usb7: USB revision 2.0 > uhub7: on usb7 > uhub7: 6 ports with 6 removable, self powered > uhub7: port 6, set config at addr 2 failed > uhub7: device problem (INVAL), disabling port 6 > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xfebffc00-0xfebffc7f irq 16 at device 0.0 on pci4 > miibus0: on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:10:5a:69:26:6b > xl0: [ITHREAD] > pci4: at device 1.0 (no driver attached) > pci4: at device 1.1 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f,0x9400-0x940f > irq 22 at device 31.2 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci2: port > 0xb000-0xb007,0xac00-0xac03,0xa880-0xa887,0xa800-0xa803,0xa480-0xa48f,0xa400-0xa40f > irq 22 at device 31.5 on pci0 > atapci2: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > acpi_button0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > cpu0: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 7F, > should be 76 [20070320] > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > p4tcc3: on cpu3 > ppc0: cannot reserve I/O port range > sc0: 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 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on > uhub2 > ums0: 16 buttons and Z dir. > uhid0: on > uhub2 > umass0: on uhub5 > Timecounters tick every 1.000 msec > ad8: 476940MB at ata4-master SATA300 > ad10: 238475MB at ata5-master SATA150 > GEOM_LABEL: Label for provider ad10s3 is ntfs/System. > acd0: DVDR at ata6-master SATA150 > ad14: 953869MB at ata7-master SATA300 > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da1 at umass-sim0 bus 0 target 0 lun 1 > da1: Removable Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present > da2 at umass-sim0 bus 0 target 0 lun 2 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 3 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install. > Trying to mount root from ufs:/dev/ad8s1a > 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-RC2 #0: Tue Dec 23 11:42:13 UTC 2008 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2666.78-MHz K8-class > CPU) > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 4 > usable memory = 4280983552 (4082 MB) > avail memory = 4119531520 (3928 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xc000-0xc0ff mem > 0xd0000000-0xdfffffff,0xfe9e0000-0xfe9effff irq 16 at device 0.0 on pci1 > vgapci1: mem 0xfe9f0000-0xfe9fffff at device 0.1 on > pci1 > uhci0: port 0xb800-0xb81f irq 16 at device > 26.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xb880-0xb89f irq 21 at device > 26.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xbc00-0xbc1f irq 18 at device > 26.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfe8ffc00-0xfe8fffff irq 18 > at device 26.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: on usb3 > uhub3: 6 ports with 6 removable, self powered > umass0: on uhub3 > pci0: at device 27.0 (no driver attached) > pcib2: irq 17 at device 28.0 on pci0 > pci3: on pcib2 > pcib3: irq 17 at device 28.4 on pci0 > pci2: on pcib3 > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem > 0xfeaffc00-0xfeafffff irq 16 at device 0.0 on pci2 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > uhci3: port 0xb080-0xb09f irq 23 at device > 29.0 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb4: on uhci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > uhci4: port 0xb400-0xb41f irq 19 at device > 29.1 on pci0 > uhci4: [GIANT-LOCKED] > uhci4: [ITHREAD] > usb5: on uhci4 > usb5: USB revision 1.0 > uhub5: on usb5 > uhub5: 2 ports with 2 removable, self powered > uhci5: port 0xb480-0xb49f irq 18 at device > 29.2 on pci0 > uhci5: [GIANT-LOCKED] > uhci5: [ITHREAD] > usb6: on uhci5 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > ehci1: mem 0xfe8ff800-0xfe8ffbff irq 23 > at device 29.7 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb7: EHCI version 1.0 > usb7: companion controllers, 2 ports each: usb4 usb5 usb6 > usb7: on ehci1 > usb7: USB revision 2.0 > uhub7: on usb7 > uhub7: 6 ports with 6 removable, self powered > uhub7: port 6, set config at addr 2 failed > uhub7: device problem (INVAL), disabling port 6 > pcib4: at device 30.0 on pci0 > pci4: on pcib4 > xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec00-0xec7f mem > 0xfebffc00-0xfebffc7f irq 16 at device 0.0 on pci4 > miibus0: on xl0 > xlphy0: <3Com internal media interface> PHY 24 on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:10:5a:69:26:6b > xl0: [ITHREAD] > pci4: at device 1.0 (no driver attached) > pci4: at device 1.1 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0xa000-0xa007,0x9c00-0x9c03,0x9880-0x9887,0x9800-0x9803,0x9480-0x948f,0x9400-0x940f > irq 22 at device 31.2 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > atapci2: port > 0xb000-0xb007,0xac00-0xac03,0xa880-0xa887,0xa800-0xa803,0xa480-0xa48f,0xa400-0xa40f > irq 22 at device 31.5 on pci0 > atapci2: [ITHREAD] > ata6: on atapci2 > ata6: [ITHREAD] > ata7: on atapci2 > ata7: [ITHREAD] > acpi_button0: on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fdc0: [FILTER] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > cpu0: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - 7F, > should be 76 [20070320] > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > p4tcc1: on cpu1 > cpu2: on acpi0 > est2: on cpu2 > p4tcc2: on cpu2 > cpu3: on acpi0 > est3: on cpu3 > p4tcc3: on cpu3 > ppc0: cannot reserve I/O port range > sc0: 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 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: on > uhub2 > ums0: 16 buttons and Z dir. > uhid0: on > uhub2 > umass1: on uhub5 > Timecounters tick every 1.000 msec > ad8: 476940MB at ata4-master SATA300 > ad10: 238475MB at ata5-master SATA150 > GEOM_LABEL: Label for provider ad10s3 is ntfs/System. > acd0: DVDR at ata6-master SATA150 > ad14: 953869MB at ata7-master SATA300 > GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install. > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #1 Launched! > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 3823MB (7830528 512 byte sectors: 255H 63S/T 487C) > da1 at umass-sim1 bus 1 target 0 lun 0 > da1: Removable Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: Attempt to query device size failed: NOT READY, Medium not present > da2 at umass-sim1 bus 1 target 0 lun 1 > da2: Removable Direct Access SCSI-0 device > da2: 1.000MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim1 bus 1 target 0 lun 2 > da3: Removable Direct Access SCSI-0 device > da3: 1.000MB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > da4 at umass-sim1 bus 1 target 0 lun 3 > da4: Removable Direct Access SCSI-0 device > da4: 1.000MB/s transfers > da4: Attempt to query device size failed: NOT READY, Medium not present > GEOM_LABEL: Label for provider da0s1 is msdosfs/4GB. > Trying to mount root from ufs:/dev/ad8s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > /tmp: mount pending error: blocks 0 files 1 > WARNING: /usr was not properly dismounted > WARNING: /var was not properly dismounted > /var: mount pending error: blocks 4 files 2 > GEOM_LABEL: Label msdosfs/4GB removed. > >>How-To-Repeat: > Install everyting (+X) from dvd -> startx -> logout -> startx > >>Fix: > > >>Release-Note: >>Audit-Trail: >>Unformatted: > _______________________________________________ > freebsd-bugs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" > From yanefbsd at gmail.com Sat Jan 3 19:50:03 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Jan 3 20:22:54 2009 Subject: misc/130103: 7.1-RC X -> systemcrash Message-ID: <200901031950.n03Jo2AZ052144@freefall.freebsd.org> The following reply was made to PR amd64/130103; it has been noted by GNATS. From: "Garrett Cooper" To: "Benjamin Stuppin" Cc: bug-followup@freebsd.org Subject: Re: misc/130103: 7.1-RC X -> systemcrash Date: Sat, 3 Jan 2009 11:46:26 -0800 On Sat, Jan 3, 2009 at 5:56 AM, Benjamin Stuppin wrote: > Hi, > updated my BIOS tody but it didn't help. :( > > Tried 7.1-RC* (amd64 and i386 for now) also 8-CURRENT without success. The ACPI-Error in dmesg also still occurs. > > Well maybe i'll give my RHD3450 a try when I'm back at home (really would prefer the r5xx Card *g*) tomorrow. A guy who wrote to my (also using the same hardware only using a RHD3450 had the same Problem but his system runs fine when he selects the ati-driver so maybe it's really a problem with the graphics adapter/drivers. I'm only wondering why 7-RELEASE runs fine. > > 7.1-RC2 i386 doesn't result in a systemcrash, it ends up in a automatic soft reboot. > > Have Fun > Ben The ACPI error I've seen -- AFAIK -- is benign on my ASUS boards even though it occurs. The behavior that you're seeing is odd though -_-... let's keep the bug list in the loop though so someone knows that there's definitely an issue with certain ATI cards on CURRENT that needs to be worked out. Two other things we should try: 1. Use another video driver (vesa for instance) in X.org and see if it still occurs. 2. Compile DDB and WITNESS support into your kernel and attach DDB prior to starting X11, then start X11 and see if you can break the kernel prior to the reboot (most likely the reboot is a panic and a kernel coredump attempt that fails). How large is your swap partition? 3. Try out PCBSD (fibonacci version -- based off of FreeBSD 7.1 RC1 I believe) and see if it occurs there. Oh and by the way the CURRENT dmesg you sent me before was empty :). Thanks, -Garrett From vwe at FreeBSD.org Sun Jan 4 16:08:08 2009 From: vwe at FreeBSD.org (vwe@FreeBSD.org) Date: Sun Jan 4 16:08:13 2009 Subject: amd64/130103: [hang] 7.1-RC X -> systemcrash Message-ID: <200901041608.n04G86h4008272@freefall.freebsd.org> Synopsis: [hang] 7.1-RC X -> systemcrash State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Sun Jan 4 16:04:35 UTC 2009 State-Changed-Why: Benjamin, to me it appears you've mixed arch binaries on your system. I'm wondering if your issue is still valid if you clean up your system (with binaries of the same $arch)? Remember to rebuild ports if you're changing $arch. Also please clarify if you're seeing system crashes (panic) or a hanging system. For a panic, we need a backtrace in the first place, for a hanging system I recommend to rebuild kernel using WITNESS. Responsible-Changed-From-To: freebsd-amd64->vwe Responsible-Changed-By: vwe Responsible-Changed-When: Sun Jan 4 16:04:35 UTC 2009 Responsible-Changed-Why: track http://www.freebsd.org/cgi/query-pr.cgi?pr=130103 From naliyev at ultel.az Mon Jan 5 06:03:21 2009 From: naliyev at ultel.az (Nadir M. Aliyev) Date: Mon Jan 5 12:13:24 2009 Subject: freebsd-amd64 Digest, Vol 290, Issue 6 In-Reply-To: <20090104120004.1747F10656C0@hub.freebsd.org> Message-ID: <20090105054507.2F399444DDF@mail.ultel.net> Its problem issues with my HP Proliant DL380 G5 Rack server too :( -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of freebsd-amd64-request@freebsd.org Sent: Sunday, January 04, 2009 4:00 PM To: freebsd-amd64@freebsd.org Subject: freebsd-amd64 Digest, Vol 290, Issue 6 Send freebsd-amd64 mailing list submissions to freebsd-amd64@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 or, via email, send a message with subject or body 'help' to freebsd-amd64-request@freebsd.org You can reach the person managing the list at freebsd-amd64-owner@freebsd.org When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-amd64 digest..." Today's Topics: 1. Re: misc/130103: 7.1-RC X -> systemcrash (Garrett Cooper) ---------------------------------------------------------------------- Message: 1 Date: Sat, 3 Jan 2009 19:50:02 GMT From: "Garrett Cooper" Subject: Re: misc/130103: 7.1-RC X -> systemcrash To: freebsd-amd64@FreeBSD.org Message-ID: <200901031950.n03Jo2AZ052144@freefall.freebsd.org> The following reply was made to PR amd64/130103; it has been noted by GNATS. From: "Garrett Cooper" To: "Benjamin Stuppin" Cc: bug-followup@freebsd.org Subject: Re: misc/130103: 7.1-RC X -> systemcrash Date: Sat, 3 Jan 2009 11:46:26 -0800 On Sat, Jan 3, 2009 at 5:56 AM, Benjamin Stuppin wrote: > Hi, > updated my BIOS tody but it didn't help. :( > > Tried 7.1-RC* (amd64 and i386 for now) also 8-CURRENT without success. The ACPI-Error in dmesg also still occurs. > > Well maybe i'll give my RHD3450 a try when I'm back at home (really would prefer the r5xx Card *g*) tomorrow. A guy who wrote to my (also using the same hardware only using a RHD3450 had the same Problem but his system runs fine when he selects the ati-driver so maybe it's really a problem with the graphics adapter/drivers. I'm only wondering why 7-RELEASE runs fine. > > 7.1-RC2 i386 doesn't result in a systemcrash, it ends up in a automatic soft reboot. > > Have Fun > Ben The ACPI error I've seen -- AFAIK -- is benign on my ASUS boards even though it occurs. The behavior that you're seeing is odd though -_-... let's keep the bug list in the loop though so someone knows that there's definitely an issue with certain ATI cards on CURRENT that needs to be worked out. Two other things we should try: 1. Use another video driver (vesa for instance) in X.org and see if it still occurs. 2. Compile DDB and WITNESS support into your kernel and attach DDB prior to starting X11, then start X11 and see if you can break the kernel prior to the reboot (most likely the reboot is a panic and a kernel coredump attempt that fails). How large is your swap partition? 3. Try out PCBSD (fibonacci version -- based off of FreeBSD 7.1 RC1 I believe) and see if it occurs there. Oh and by the way the CURRENT dmesg you sent me before was empty :). Thanks, -Garrett ------------------------------ _______________________________________________ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" End of freebsd-amd64 Digest, Vol 290, Issue 6 ********************************************* From bugmaster at FreeBSD.org Mon Jan 5 11:06:49 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 5 12:18:58 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200901051106.n05B6lxS002706@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 kgysmits at gmail.com Mon Jan 5 19:53:45 2009 From: kgysmits at gmail.com (Koen Smits) Date: Mon Jan 5 20:11:26 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" Message-ID: Hello all, I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. This CPU is fully 64bit capable. But, when I try to boot Disc1 from an IDE CD-ROM I get the error "cpu doesn't support long mode", which implies the CPU can't do 64bit, and booting halts asking for a kernel. The first thing I tried was running ubuntu 8.10 64bit. It installs and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also boots and installs normally! Any help on fixing this is much appreciated. System specs: VIA VB8001 4GB RAM Intel CT NIC (PCIe) Intel 2915abg Wireless (miniPCI) IDE Master: Kingston Ultimate 2GB CF IDE Slave: Samsung CD-ROm drive Sincerely, Koen Smits PS. I'm new to the mailing list concept. If i mess something up, please let me know. From jkim at FreeBSD.org Mon Jan 5 21:04:10 2009 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Mon Jan 5 21:04:17 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: References: Message-ID: <200901051543.12582.jkim@FreeBSD.org> On Monday 05 January 2009 02:24 pm, Koen Smits wrote: > Hello all, > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on > my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. > This CPU is fully 64bit capable. But, when I try to boot Disc1 from > an IDE CD-ROM I get the error "cpu doesn't support long mode", > which implies the CPU can't do 64bit, and booting halts asking for > a kernel. > The first thing I tried was running ubuntu 8.10 64bit. It installs > and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also > boots and installs normally! > Any help on fixing this is much appreciated. See: http://svn.freebsd.org/viewvc/base?view=revision&revision=183667 http://svn.freebsd.org/viewvc/base?view=revision&revision=183823 I am not sure removing Via CPU support was intentional, though. Jung-uk Kim From jkim at FreeBSD.org Mon Jan 5 21:16:59 2009 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Mon Jan 5 21:17:05 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: References: Message-ID: <200901051616.39069.jkim@FreeBSD.org> On Monday 05 January 2009 02:24 pm, Koen Smits wrote: > Hello all, > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on > my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. > This CPU is fully 64bit capable. But, when I try to boot Disc1 from > an IDE CD-ROM I get the error "cpu doesn't support long mode", > which implies the CPU can't do 64bit, and booting halts asking for > a kernel. > The first thing I tried was running ubuntu 8.10 64bit. It installs > and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also > boots and installs normally! > Any help on fixing this is much appreciated. See: http://svn.freebsd.org/viewvc/base?view=revision&revision=183667 http://svn.freebsd.org/viewvc/base?view=revision&revision=183823 I am not sure removing Via CPU support was intentional, though. Jung-uk Kim From kostikbel at gmail.com Tue Jan 6 00:24:59 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Tue Jan 6 00:25:05 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: References: Message-ID: <20090105203355.GO93900@deviant.kiev.zoral.com.ua> On Mon, Jan 05, 2009 at 08:24:58PM +0100, Koen Smits wrote: > Hello all, > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on my VIA > VB8001, which is a mini-ITX board with the new VIA Nano CPU. This CPU is > fully 64bit capable. But, when I try to boot Disc1 from an IDE CD-ROM I get > the error "cpu doesn't support long mode", which implies the CPU can't do > 64bit, and booting halts asking for a kernel. > The first thing I tried was running ubuntu 8.10 64bit. It installs and runs > fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also boots and installs > normally! > Any help on fixing this is much appreciated. > > System specs: > VIA VB8001 > 4GB RAM > Intel CT NIC (PCIe) > Intel 2915abg Wireless (miniPCI) > IDE Master: Kingston Ultimate 2GB CF > IDE Slave: Samsung CD-ROm drive > > Sincerely, > > Koen Smits > > PS. I'm new to the mailing list concept. If i mess something up, please let > me know. This is due to sys/boot/i386/libi386/bootinfo64.c, bi_checkcpu() function, that explicitely verifies that CPU is made by Intel or AMD. Remove strcmp() checks and rebuild the loader. -------------- 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/20090106/94cbe584/attachment.pgp From tinderbox at freebsd.org Tue Jan 6 17:43:27 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Jan 6 17:43:34 2009 Subject: [releng_6 tinderbox] failure on amd64/amd64 Message-ID: <20090106174324.2C919241BA@freebsd-legacy.sentex.ca> TB --- 2009-01-06 17:41:34 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-06 17:41:34 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2009-01-06 17:41:34 - cleaning the object tree TB --- 2009-01-06 17:42:15 - cvsupping the source tree TB --- 2009-01-06 17:42:15 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2009-01-06 17:42:24 - building world TB --- 2009-01-06 17:42:24 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-06 17:42:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-06 17:42:24 - TARGET=amd64 TB --- 2009-01-06 17:42:24 - TARGET_ARCH=amd64 TB --- 2009-01-06 17:42:24 - TZ=UTC TB --- 2009-01-06 17:42:24 - __MAKE_CONF=/dev/null TB --- 2009-01-06 17:42:24 - cd /src TB --- 2009-01-06 17:42:24 - /usr/bin/make -B buildworld >>> 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 [...] ===> usr.sbin/wicontrol (cleandir) rm -f wicontrol wicontrol.o wicontrol.8.gz wicontrol.8.cat.gz rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> usr.sbin/wpa (cleandir) ===> usr.sbin/wpa/wpa_supplicant (cleandir) "Makefile", line 14: Malformed conditional (${MK_EXAMPLES} != "no") "Makefile", line 17: if-less endif make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /src/usr.sbin/wpa. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-06 17:43:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-06 17:43:23 - ERROR: failed to build world TB --- 2009-01-06 17:43:23 - 25.09 user 11.80 system 109.20 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From jungleji at gmail.com Wed Jan 7 06:20:05 2009 From: jungleji at gmail.com (Ji YongGang) Date: Wed Jan 7 12:32:13 2009 Subject: amd64/119936 Message-ID: <200901070620.n076K4W1096714@freefall.freebsd.org> The following reply was made to PR amd64/119936; it has been noted by GNATS. From: Ji YongGang To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/119936 Date: Wed, 07 Jan 2009 13:50:00 +0800 It's fixed on FreeBSD 7.1 amd64 and i386 installer disc1. -- Ji YongGang From linimon at FreeBSD.org Thu Jan 8 08:35:01 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Jan 8 12:44:17 2009 Subject: amd64/119936: [install] FreeBSD 7.0-RC1 amd64 and i386 installer disc stalled on booting. Message-ID: <200901080835.n088Z1YI083495@freefall.freebsd.org> Synopsis: [install] FreeBSD 7.0-RC1 amd64 and i386 installer disc stalled on booting. State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Thu Jan 8 08:34:46 UTC 2009 State-Changed-Why: Submitter notes that this has been fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=119936 From kgysmits at gmail.com Thu Jan 8 15:50:02 2009 From: kgysmits at gmail.com (Koen Smits) Date: Thu Jan 8 15:50:17 2009 Subject: amd64/130303: FreeBSD 7.1-RELEASE amd64 cannot boot on VIA Nano equipped systems Message-ID: <200901081540.n08FeYW3055354@www.freebsd.org> >Number: 130303 >Category: amd64 >Synopsis: FreeBSD 7.1-RELEASE amd64 cannot boot on VIA Nano equipped systems >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 08 15:50:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Koen Smits >Release: 7.1-RELEASE >Organization: >Environment: >Description: boot loader checks if the 64bit CPU is Intel or AMD, obviously VIA is neither of them. boot process reports "CPU does not support long mode" and asks for kernel. See simple patch below. Maybe this check should not be performed at all? Note that VIA CPU's allow you to change the vendorstring. This could lead to more trouble. >How-To-Repeat: Boot 7.1-RELEASE Disc1 on VIA Nano equipped system. (VIA VB8001 for example) >Fix: /usr/src/sys/boot/i386/libi386/bootinfo64.c: Line 152+: ! 152: /* Check for vendors that support AMD features. */ ! 153: if (strncmp(cpu_vendor, "GenuineIntel", 12) != 0 && ! 154: strncmp(cpu_vendor, "AuthenticAMD", 12) != 0) ! 155: return (0); change to: /* Check for vendors that support AMD features. */ if (strncmp(cpu_vendor, "GenuineIntel", 12) != 0 && strncmp(cpu_vendor, "AuthenticAMD", 12) != 0 && strncmp(cpu_vendor, "CentaurHauls", 12) != 0) return (0); >Release-Note: >Audit-Trail: >Unformatted: From dchagin at freebsd.org Fri Jan 9 23:27:39 2009 From: dchagin at freebsd.org (Chagin Dmitry) Date: Sat Jan 10 03:58:53 2009 Subject: linuxulator64 status Message-ID: <20090109225419.GA14444@dchagin.dialup.corbina.ru> hi, /me ready to present x86_64 linuxulator patch (including latest futexes work, latest ELF Notes patch) for testing. also the linux_base-f8 port offered with support x86_64 and compat_i386 emulation simultaneously. here patch against HEAD http://code.google.com/p/lnxx64/downloads/list known bugs: 1) linux_base-f8 has incomplete pkg-plist and probably i386 libs. 2) i386 && x86_64 emulation layers have various sysctls (temporarily???). I shall glad for remarks, proposals and results of testing. thnx! -- Have fun! chd From gb at clozure.com Sat Jan 10 16:40:07 2009 From: gb at clozure.com (Gary Byers) Date: Sat Jan 10 16:52:48 2009 Subject: amd64/130355: i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 Message-ID: <200901110035.n0B0ZDX5089905@www.freebsd.org> >Number: 130355 >Category: amd64 >Synopsis: i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 11 00:40:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Gary Byers >Release: 7.1-RELEASE/amd64 >Organization: Clozure Associates >Environment: FreeBSD f71.abq.clozure.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: i386_set_fsbase(void *addr) has the effect of causing memory references relative to %fs to reference the linear address "addr"; part of this effect is achieved by loading a segment descriptor (GSEL(GUFS_SEL, SEL_UPL), which is generally = 0x13) into %fs on return from the sysarch syscall. This works as expected on (at least) i386 versions of 6.4-RELEASE, 7.0-RELEASE, and 7.1-RELEASE and on amd64 versions of 6.4-RELEASE and 7.0-RELEASE, but on 7.1-RELEASE/amd64 the i386_set_fsbase() call returns 0 but %fs is unchanged on return and subsequent attempts to reference memory relative to %fs seem to be equivalent to references relative to address 0. >How-To-Repeat: Compile (in a 32-bit FreeBSD/i386 environment) a small program that uses i386_set_fsbase() and checks to ensure that %fs has changed on successful return from the call to i386_set_fsbase(). Run the program on i386 versions of FreeBSD (6.4, 7.0, 7.1) and on amd64 versions of 6.4 and 7.0 and note that %fs is changed by the syscall. Run the program on 7.1-RELEASE/amd64 and note that it fails. (I'm not really sure if I'm supposed to provide a simple test case on the web form that I'm using to report this; I can easily do so if requested.) >Fix: Unknown. To the extent that I understand the issue, it seems to have to do with code that tries to ensure that the correct value is loaded into %fs on return from the syscall and on subsequent context switches; the code that actually sets the fsbase msr seems to be unchanged between the released versions of 7.0 and 7.1. >Release-Note: >Audit-Trail: >Unformatted: From xxjack12xx at gmail.com Sat Jan 10 22:40:03 2009 From: xxjack12xx at gmail.com (Jack) Date: Sat Jan 10 22:40:15 2009 Subject: amd64/130365: Elitegroup A780GM-A Chipset:AMD 780G&SB700 IDE controller not recognized Message-ID: <200901110634.n0B6YjfX094759@www.freebsd.org> >Number: 130365 >Category: amd64 >Synopsis: Elitegroup A780GM-A Chipset:AMD 780G&SB700 IDE controller not recognized >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 11 06:40:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Jack >Release: 7.1-RELEASE >Organization: >Environment: FreeBSD jack.musirc.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The dmesg output shows: ata0: 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=7f ostat1=7f ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat1=0x7f err=0xff lsb=0xff msb=0xff ata0: reset tp2 stat0=ff stat1=ff devices=0x0 None of the IDE devices are detected by the system. Chipset is AMD 780G and SB700 >How-To-Repeat: Boot FreeBSD 7.1 from disk >Fix: >Release-Note: >Audit-Trail: >Unformatted: From xxjack12xx at gmail.com Sat Jan 10 23:10:07 2009 From: xxjack12xx at gmail.com (Jack) Date: Sat Jan 10 23:10:15 2009 Subject: amd64/130368: Switching from xorg to console locks up computer Message-ID: <200901110706.n0B76SB1009733@www.freebsd.org> >Number: 130368 >Category: amd64 >Synopsis: Switching from xorg to console locks up computer >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 11 07:10:05 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Jack >Release: 7.1-RELEASE >Organization: >Environment: FreeBSD jack.musirc.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Switching from xorg to the console causes the system to freeze. Attached is the dmesg output Motherboard is ECS A780GM-A >How-To-Repeat: start xorg and logout or ctrl+alt+backspace and the system hangs and does not respond to any keyboard actions. >Fix: Patch attached with submission follows: ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec md0: Preloaded image 4194304 bytes at 0xffffffff80c4be40 ad4: 476940MB at ata2-master SATA300 ad6: 381554MB at ata3-master SATA300 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/md0 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...502 145 69 67 65 2 2 2 0 0 0 done All buffers synced. Copyright (c) 1992-2009 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-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80cc0000. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff80cc01d0. Preloaded elf obj module "/boot/kernel/snd_ich.ko" at 0xffffffff80cc0838. Preloaded elf obj module "/boot/kernel/accf_data.ko" at 0xffffffff80cc0e20. Preloaded elf obj module "/boot/kernel/accf_http.ko" at 0xffffffff80cc12d0. Calibrating clock(s) ... i8254 clock: 1193218 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3200136328 Hz CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ (3200.14-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f 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 = 8541208576 (8145 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000dc3000 - 0x00000000dfeaffff, 3742289920 bytes (913645 pages) 0x0000000100000000 - 0x000000020e16bfff, 4531339264 bytes (1106284 pages) avail memory = 8257953792 (7875 MB) ACPI APIC Table: <110608 APIC1133> 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 @ 0x0xf9e40/0x0014 (v 0 ACPIAM) ACPI: RSDT @ 0x0xdfeb0000/0x0038 (v 1 110608 RSDT1133 0x20081106 MSFT 0x00000097) ACPI: FACP @ 0x0xdfeb0200/0x0084 (v 2 110608 FACP1133 0x20081106 MSFT 0x00000097) ACPI: DSDT @ 0x0xdfeb0440/0x4D44 (v 1 1AAAA 1AAAA000 0x00000000 INTL 0x20051117) ACPI: FACS @ 0x0xdfebe000/0x0040 ACPI: APIC @ 0x0xdfeb0390/0x006C (v 1 110608 APIC1133 0x20081106 MSFT 0x00000097) ACPI: MCFG @ 0x0xdfeb0400/0x003C (v 1 110608 OEMMCFG 0x20081106 MSFT 0x00000097) ACPI: OEMB @ 0x0xdfebe040/0x0071 (v 1 110608 OEMB1133 0x20081106 MSFT 0x00000097) ACPI: HPET @ 0x0xdfeb5190/0x0038 (v 1 110608 OEMHPET 0x20081106 MSFT 0x00000097) 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 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 ath_rate: version 1.2 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 wlan_amrr: wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: io: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Jan 1 2009 08:57:24) acpi0: <110608 RSDT1133> on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) AcpiOsDerivePciId: \\_SB_.PCI0.RS78.NB2_ -> bus 0 dev 0 func 0 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 AcpiOsDerivePciId: \\_SB_.PCI0.SATA.SACS -> bus 0 dev 17 func 0 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi0: reservation of fee00000, 1000 (3) failed acpi0: reservation of ffb80000, 80000 (3) failed acpi0: reservation of fec10000, 20 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, dfe00000 (3) failed ACPI HPET table warning: Sequence is non-zero (2) ACPI timer: 0/3 0/5 0/3 0/3 0/3 0/3 1/2 0/3 0/3 0/3 -> 1 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 7 N 0 4 7 10 11 12 14 15 Validation 0 7 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 4 N 0 4 7 10 11 12 14 15 Validation 0 4 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 4 7 10 11 12 14 15 Validation 0 10 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 4 7 10 11 12 14 15 Validation 0 10 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 4 7 10 11 12 14 15 Validation 0 255 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 4 7 10 11 12 14 15 Validation 0 255 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 4 7 10 11 12 14 15 Validation 0 11 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 4 7 10 11 12 14 15 Validation 0 255 N 0 4 7 10 11 12 14 15 After Disable 0 255 N 0 4 7 10 11 12 14 15 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_hpet0: vend: 0x4353 rev: 0x1 num: 3 hz: 14318180 opts: legacy_route Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1022, dev=0x9600, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x9602, 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=0x1022, dev=0x9606, revid=0x00 domain=0, bus=0, slot=6, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4391, revid=0x00 domain=0, bus=0, slot=17, func=0 class=01-06-01, 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.17.INTA pcib0: slot 17 INTA hardwired to IRQ 22 found-> vendor=0x1002, dev=0x4397, revid=0x00 domain=0, bus=0, slot=18, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0102, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 map[10]: type Memory, range 32, base 0xfe7fe000, size 12, enabled pcib0: matched entry for 0.18.INTA pcib0: slot 18 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4398, revid=0x00 domain=0, bus=0, slot=18, func=1 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=a, irq=7 map[10]: type Memory, range 32, base 0xfe7fd000, size 12, enabled pcib0: matched entry for 0.18.INTA pcib0: slot 18 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4396, revid=0x00 domain=0, bus=0, slot=18, func=2 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0102, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=4 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.18.INTB pcib0: slot 18 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4397, revid=0x00 domain=0, bus=0, slot=19, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[10]: type Memory, range 32, base 0xfe7fc000, size 12, enabled pcib0: matched entry for 0.19.INTA pcib0: slot 19 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4398, revid=0x00 domain=0, bus=0, slot=19, func=1 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=a, irq=10 map[10]: type Memory, range 32, base 0xfe7f7000, size 12, enabled pcib0: matched entry for 0.19.INTA pcib0: slot 19 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x4396, revid=0x00 domain=0, bus=0, slot=19, func=2 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0102, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe7f6800, size 8, enabled pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 19 found-> vendor=0x1002, dev=0x4385, revid=0x3a domain=0, bus=0, slot=20, func=0 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0403, statreg=0xd230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x439c, revid=0x00 domain=0, bus=0, slot=20, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 MSI supports 2 messages map[20]: type I/O Port, range 32, base 0xff00, size 4, enabled 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=7 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 64, base 0xfe7f0000, size 14, enabled pcib0: matched entry for 0.20.INTA pcib0: slot 20 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x439d, 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=0x1002, dev=0x4399, revid=0x00 domain=0, bus=0, slot=20, func=5 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0102, 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 0xfe7f5000, size 12, enabled pcib0: matched entry for 0.20.INTC pcib0: slot 20 INTC hardwired to IRQ 18 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: 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 0xfa000000-0xfbffffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1002, dev=0x9610, revid=0x00 domain=0, bus=1, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x4010, 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 Prefetchable Memory, range 32, base 0xfa000000, size 25, enabled pcib1: requested memory range 0xfa000000-0xfbffffff: good map[14]: type I/O Port, range 32, base 0xc000, size 8, enabled pcib1: requested I/O range 0xc000-0xc0ff: in range map[18]: type Memory, range 32, base 0xfe9f0000, size 16, enabled pcib1: requested memory range 0xfe9f0000-0xfe9fffff: good 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 vgapci0: port 0xc000-0xc0ff mem 0xfa000000-0xfbffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 pcib2: irq 18 at device 6.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: prefetched decode 0xfdf00000-0xfdffffff pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.PCE6 - AE_NOT_FOUND pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x10ec, dev=0x8168, revid=0x02 domain=0, bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0107, 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 MSI-X supports 2 messages in map 0x20 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 map[20]: type Prefetchable Memory, range 64, base 0xfdff0000, size 16, enabled pcib2: requested memory range 0xfdff0000-0xfdffffff: good pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 18 pcib2: slot 0 INTA is routed to irq 18 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci2 re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xfeaff000 re0: MSI count : 1 re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: bpf attached re0: Ethernet address: 00:21:97:0f:0c:9f ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49 re0: [MPSAFE] re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 17.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: on atapci0 ata2: SATA connect time=0ms ata2: SIGNATURE: 00000101 ata2: ahci_reset devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 ata3: SATA connect time=0ms ata3: SIGNATURE: 00000101 ata3: ahci_reset devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci0 ata4: SATA connect status=00000000 ata4: ahci_reset devices=0x0 ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci0 ata5: SATA connect status=00000000 ata5: ahci_reset devices=0x0 ata5: [MPSAFE] ata5: [ITHREAD] ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 18.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fe000 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 51 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe7fd000-0xfe7fdfff irq 16 at device 18.1 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fd000 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfe7ff000-0xfe7ff0ff irq 17 at device 18.2 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe7ff000 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 52 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] ehci0: Dropped interrupts workaround enabled usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.0 on pci0 ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fc000 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 3 ports with 3 removable, self powered ohci3: mem 0xfe7f7000-0xfe7f7fff irq 18 at device 19.1 on pci0 ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7f7000 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 3 ports with 3 removable, self powered ehci1: mem 0xfe7f6800-0xfe7f68ff irq 19 at device 19.2 on pci0 ehci1: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe7f6800 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 53 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] ehci1: Dropped interrupts workaround enabled usb5: EHCI version 1.0 usb5: companion controllers, 3 ports each: usb3 usb4 usb5: on ehci1 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 6 ports with 6 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: 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: 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=7f ostat1=7f ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff ata0: stat1=0x7f err=0xff lsb=0xff msb=0xff ata0: reset tp2 stat0=ff stat1=ff devices=0x0 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata0: [ITHREAD] pci0: at device 20.2 (no driver attached) isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: 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: on pcib3 pci3: domain=0, physical bus=3 found-> vendor=0x8086, dev=0x1229, revid=0x0c domain=0, bus=3, slot=7, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfebff000, size 12, enabled pcib3: requested memory range 0xfebff000-0xfebfffff: good map[14]: type I/O Port, range 32, base 0xe800, size 6, enabled pcib3: requested I/O range 0xe800-0xe83f: in range map[18]: type Memory, range 32, base 0xfebc0000, size 17, enabled pcib3: requested memory range 0xfebc0000-0xfebdffff: good pcib3: matched entry for 3.7.INTA pcib3: slot 7 INTA hardwired to IRQ 22 fxp0: port 0xe800-0xe83f mem 0xfebff000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci3 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebff000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1229 8086 0040 000c fxp0: Dynamic Standby mode is disabled miibus1: on fxp0 inphy0: PHY 1 on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:02:b3:33:cc:c1 fxp0: [MPSAFE] fxp0: [ITHREAD] ohci4: mem 0xfe7f5000-0xfe7f5fff irq 18 at device 20.5 on pci0 ohci4: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7f5000 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb6: OHCI version 1.0, legacy support usb6: SMM does not respond, resetting usb6: on ohci4 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered acpi_button0: on acpi0 acpi_tz0: on acpi0 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: 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 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: failed to reset the aux device. acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 ioapic0: routing intpin 6 (ISA IRQ 6) to vector 56 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 cpu0: on acpi0 cpu0: switching to generic Cx mode acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x810 powernow0: on cpu0 powernow0: STATUS: 0x3104120604180218 powernow0: STATUS: maxfid: 0x18 powernow0: STATUS: maxvid: 0x04 device_attach: powernow0 attach returned 6 cpu1: on acpi0 powernow1: on cpu1 powernow1: STATUS: 0x3104120604180218 powernow1: STATUS: maxfid: 0x18 powernow1: STATUS: maxvid: 0x04 device_attach: powernow1 attach returned 6 ex_isa_identify() atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 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: at iomem 0xd1000-0xd27ff on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding ioapic0: routing intpin 4 (ISA IRQ 4) to vector 57 sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0 0 0 0 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices ums0: on uhub0 ums0: 3 buttons and Z dir. Device configuration finished. Reducing kern.maxvnodes 235635 -> 100000 procfs registered lapic: Divisor 2, Frequency 100004269 hz Timecounter "TSC" frequency 3200136328 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: 476940MB at ata2-master SATA300 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: Silicon Image check3 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: 381554MB at ata3-master SATA300 ad6: 781422768 sectors [775221C/16H/63S] 16 sectors/interrupt 1 depth queue 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 4 to local APIC 1 ioapic0: Assigning ISA IRQ 6 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 1 ioapic0: Assigning ISA IRQ 14 to local APIC 0 ioapic0: Assigning PCI IRQ 16 to local APIC 1 ioapic0: Assigning PCI IRQ 17 to local APIC 0 ioapic0: Assigning PCI IRQ 18 to local APIC 1 ioapic0: Assigning PCI IRQ 19 to local APIC 0 ioapic0: Assigning PCI IRQ 22 to local APIC 1 GEOM: new disk ad4 GEOM: new disk ad6 Trying to mount root from ufs:/dev/ad4s1a start_init: trying /sbin/init acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x5a acpi: bad write to port 0x000 (8), val 0x7 acpi: bad write to port 0x001 (8), val 0x7 acpi: bad write to port 0x000 (8), val 0x30 acpi: bad read from port 0x001 (8) acpi: bad read from port 0x000 (8) acpi: bad write to port 0x000 (8), val 0xa5 Linux ELF exec handler installed linprocfs registered ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Sun Jan 11 14:52:31 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Sun Jan 11 14:52:37 2009 Subject: amd64/130365: [ata] Elitegroup A780GM-A Chipset:AMD 780G&SB700 IDE controller not recognized Message-ID: <200901112252.n0BMqU1q094902@freefall.freebsd.org> Synopsis: [ata] Elitegroup A780GM-A Chipset:AMD 780G&SB700 IDE controller not recognized State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Sun Jan 11 22:50:36 UTC 2009 State-Changed-Why: To submitter: are you able to give the output of "pciconf -lv" for the ATA controller in question? If the machine doesn't have FreeBSD on it at the moment, you can boot the fixit CD or similar to obtain the output of that command Responsible-Changed-From-To: freebsd-amd64->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Sun Jan 11 22:50:36 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=130365 From gb at clozure.com Sun Jan 11 23:40:04 2009 From: gb at clozure.com (Gary Byers) Date: Sun Jan 11 23:40:14 2009 Subject: amd64/130355: [kernel] i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 Message-ID: <200901120740.n0C7e3Ho027482@freefall.freebsd.org> The following reply was made to PR amd64/130355; it has been noted by GNATS. From: Gary Byers To: bug-followup@FreeBSD.org, gb@clozure.com Cc: Subject: Re: amd64/130355: [kernel] i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 Date: Sun, 11 Jan 2009 23:03:18 -0700 My claim that i386_set_fsbase() changed the value of %fs when used on other amd64 kernels was incorrect. As far as I can tell, there's no 7.1 kernel bug here. From linimon at FreeBSD.org Mon Jan 12 00:58:40 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Jan 12 04:19:53 2009 Subject: amd64/130355: [kernel] i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 Message-ID: <200901120858.n0C8wdmD090916@freefall.freebsd.org> Synopsis: [kernel] i386_set_fsbase() doesn't seem to set %fs for 32-bit process under 7.1/amd64 State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Mon Jan 12 08:58:22 UTC 2009 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=130355 From bugmaster at FreeBSD.org Mon Jan 12 03:06:49 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 12 04:25:20 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200901121106.n0CB6mrl091918@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/130368 amd64 Switching from xorg to console locks up computer o amd64/130303 amd64 [boot] [patch] FreeBSD 7.1-RELEASE amd64 cannot boot o 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/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 90 problems total. From jkim at FreeBSD.org Mon Jan 12 08:23:54 2009 From: jkim at FreeBSD.org (jkim@FreeBSD.org) Date: Mon Jan 12 08:24:01 2009 Subject: amd64/130303: [boot] [patch] FreeBSD 7.1-RELEASE amd64 cannot boot on VIA Nano equipped systems Message-ID: <200901121623.n0CGNqhi036581@freefall.freebsd.org> Synopsis: [boot] [patch] FreeBSD 7.1-RELEASE amd64 cannot boot on VIA Nano equipped systems Responsible-Changed-From-To: freebsd-amd64->jkim Responsible-Changed-By: jkim Responsible-Changed-When: Mon Jan 12 16:23:21 UTC 2009 Responsible-Changed-Why: I will take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=130303 From wuxiuchao at gmail.com Mon Jan 12 21:10:02 2009 From: wuxiuchao at gmail.com (Xiuchao Wu) Date: Mon Jan 12 21:26:11 2009 Subject: amd64/130483: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server Message-ID: <200901130502.n0D5275X095567@www.freebsd.org> >Number: 130483 >Category: amd64 >Synopsis: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 13 05:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Xiuchao Wu >Release: FreeBSD 7.0 >Organization: National University of Singapore >Environment: FreeBSD 7.0/7.1 Release >Description: Computer: Dell PowerEdge T300 Server NICs: Myricom 10G-PCIE-8AL-C OS: FreeBSD 7.0/7.1 Release After I rebuild the kernel (to include NIC driver "mxge") and reboot, kernel panic occurs and the computer is automatically rebooted. After contacting with engineers of Myricom, they suggest to disable message signaled interrupt (MSI) in /boot/loader.conf and these NICs can work now. " hw.pci.enable_msix=0 hw.pci.enable_msi=0 " However, MSI is really very important for high speed data transmission. Huge number of packets generate many interruptions. Considering that Fedora 9 works well on the same computer, it may be a bug of FreeBSD. Below is the screen when kernel panic occurs. ...... p4tcc3: on cpu3 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci3: on pcib1 pcib2: at device 3.0 on pci0 pci4: on pcib2 pcib3: at device 4.0 on pci0 pci5: on pcib3 mxge0: mem 0xd8000000-0xd8ffffff, 0xdfa00000-0xdfafffff irq 16 at device 0.0 on pci5 panic: nexus_add_irq: failed ..... Best Regards, Xiuchao Wu (wuxiuchao@gmail.com) >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From fjo at ogris.de Tue Jan 13 02:40:02 2009 From: fjo at ogris.de (Felix J. Ogris) Date: Tue Jan 13 04:19:33 2009 Subject: amd64/130494: netbooting BTX fails on amd64 Message-ID: <200901131038.n0DAcQx2066577@www.freebsd.org> >Number: 130494 >Category: amd64 >Synopsis: netbooting BTX fails on amd64 >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: Tue Jan 13 10:40:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Felix J. Ogris >Release: 7.1-RELEASE amd64 >Organization: DTS Systeme GmbH >Environment: not possible due to BTX loader issues (see full description below) >Description: Hi, I am trying to netboot 7.1 amd64 on bare metal systems (HP blade class) and within VMware ESXi. In both scenarios I use PXE to boot memdisk from the Syslinux project which then loads a FreeBSD harddisk image. This disk image contains the BTX loader (as created by "bsdlabel -w -B") and the /boot directory from the 7.1-RELEASE-bootonly.iso. Booting this fails with various errors. Either the BTX halts and dumps CPU registers until the machine is reset, or BTX stops after loading text segment and powers off the machine after a while. Booting 7.0-RELEASE amd64 this way works fine, as 7.1-RELEASE i386 and 7.0-RELEASE i386 does. CD boot works fine for all 4 releases. Don't hesitate to contact me by mail if you need further info, dumps, etc. Regards Felix >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From gb at clozure.com Tue Jan 13 18:10:02 2009 From: gb at clozure.com (Gary Byers) Date: Tue Jan 13 18:10:09 2009 Subject: amd64/130526: fsbase issues for i386 processes running on 7.1-RELEASE/amd64 Message-ID: <200901140201.n0E214RK006767@www.freebsd.org> >Number: 130526 >Category: amd64 >Synopsis: fsbase issues for i386 processes running on 7.1-RELEASE/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: Wed Jan 14 02:10:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Gary Byers >Release: 7.1-RELEASE/amd64 >Organization: Clozure Associates >Environment: FreeBSD boddhi.abq.clozure.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: After using i386_set_fsbase() to make the %fs segment register point to a specified linear address, 32-bit processes running on 7.1-RELEASE amd64 can't reliably use %fs to access memory. Exactly when the process loses the ability to use %fs is unclear, but the enclosed example program seems to show that that ability is lost after a call to sleep(). I'm not familiar enough with x8664 system-level architecture to be fully comfortable in describing the symptom, but my limited understanding suggests that the symptom is consistent with the fsbase MSR not being restored correctly. >How-To-Repeat: The attached shell archive contains source to a small C program which seems to demonstrate the problem. (It likely needs to be compiled on a 32-bit FreeBSD system.) The program establishes a signal handler for SIGBUS and SIGSEGV; the handler simply prints some context information and exits. The program then allocates a 100-byte pointer ("p") via malloc() and uses the pointer returned as an argument to i386_set_fsbase(); this should have the effect of making the %fs segment register address the pointer, so the byte or word at %fs:0 is equivalent to p[0]. The program then executes 100 iterations of a loop which stores a 32-bit value at the malloc'ed pointer's address, reads the 32-bit word at %fs:0, sleeps for 1 second, and reads the word at %fs:0 again. After each read of %fs:0, the value read relative to %fs is compared to the value stored at the pointer address; if the values differ, the code calls i386_set_fsbase() to see the adderss it returns by reference matches the pointer address, prints these values, and exits. The program should therefore do little of interest and take about 100 seconds to do so. When run on a 7.1 amd64 release kernel, the program segfaults, usually after sleeping on the first iteration. (So the first attempt to reference memory at %fs:0 succeeded as expected; attempting to read the same value after calling sleep() fails.) This may indicate that the fsbase MSR is not restored correctly after context switch and/or syscall return. >Fix: Unknown. A few days ago, I submitted an invalid bug report (130355) which claimed that this symptom was caused by failure to set %fs to the proper selector on return from i386_set_fsbase() on 7.1/amd64. No amd64 kernel changes the %fs selector in the implementation of i386_set_fsbase; 64-bit kernels do arrange that the "fsbase" MSR is set appropriately. It seems that this works correctly (the test program can use %fs before sleeping on the first iteration), but that the fsbase MSR isn't set correctly (or something like that ...) on syscall return or after context switch, in at least some cases. Patch attached with submission follows: # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # i386_set_fsbase_test.c # echo x - i386_set_fsbase_test.c sed 's/^X//' >i386_set_fsbase_test.c << 'e02ffb4f5ccf0ea67f579a83c1cccce4' X/* This program should be compiled in a 32-bit i386 FreeBSD environment. */ X X#include X#include X#include X#include X#include X#include X#include X X Xvoid Xinstall_signal_handler(int signo, void * handler) X{ X struct sigaction sa; X X sa.sa_sigaction = (void *)handler; X sigfillset(&sa.sa_mask); X sa.sa_flags = SA_SIGINFO; X X sigaction(signo, &sa, NULL); X} X Xvoid *p, *check = NULL; Xint i; Xbool after_sleep = false; X Xvoid Xsignal_handler(int signo, siginfo_t *info, void *context) X{ X i386_get_fsbase(&check); X X fprintf(stderr, "terminating with signal %d on iteration %d, %s sleep, address = 0x%x, p = 0x%x, fsbase = 0x%x\n", X signo, X i, X after_sleep ? "after" : "before", X (uintptr_t)info->si_addr, X (uintptr_t)p, (uintptr_t)check); X exit(5); X X} X X/* return the contents of the first 32-bit word addressed by %fs */ Xunsigned long Xread_fs_contents() X{ X unsigned long res; X X __asm__ volatile ("movl %%fs:0,%0" : "=r" (res)); X return res; X} X X Xmain() X{ X int status; X X install_signal_handler(SIGBUS, signal_handler); X install_signal_handler(SIGSEGV, signal_handler); X p = malloc(100); X status = i386_set_fsbase(p); X if (status != 0) { X perror("i386_set_fsbase"); X exit(1); X } X /* it should now be true that %fs addresses the pointer 'p'; if we X store a 32-bit value at 'p', we should be able to read that X value back via read_fs_contents(), without getting any sort X of bus fault. X This seems to be true of all 32-bit FreeBSD kernels that I've X tried it on and is true of the 64-bit 6.4-RELEASE and 7.0-RELEASE; X it does not seem to be true of the 7.1/amd64-RELEASE kernel. X */ X for (i = 0; i < 100; i++) { X *((unsigned long *)p) = i; X after_sleep = false; X if (read_fs_contents() != i) { X i386_get_fsbase(&check); X fprintf (stderr, "%%fs base may have changed, now 0x%x, should be 0x%x\n",(uintptr_t)check,(uintptr_t)p); X exit(2); X } X sleep(1); X after_sleep = true; X if (read_fs_contents() != i) { X i386_get_fsbase(&check); X fprintf (stderr, "after sleep, %%fs base may have changed, now 0x%x, should be 0x%x\n",(uintptr_t)check,(uintptr_t)p); X exit(3); X } X } X exit(0); X} X e02ffb4f5ccf0ea67f579a83c1cccce4 exit >Release-Note: >Audit-Trail: >Unformatted: From nadir at ultel.net Tue Jan 13 23:40:02 2009 From: nadir at ultel.net (Nadir) Date: Tue Jan 13 23:40:08 2009 Subject: amd64/130536: not Message-ID: <200901140735.n0E7Zwu8071952@www.freebsd.org> >Number: 130536 >Category: amd64 >Synopsis: not >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 14 07:40:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Nadir >Release: 7.1-RELEASE-amd64 >Organization: Ultel >Environment: 7.1-RELEASE-amd64 >Description: hi. i have problems. i have HP Proliant DL 380 G5 server. when i insert installation cd and boot with ACPI DISABLED MODE my server gives kernel errors. but its not issues with i386 32bit platform. CPU: 2 x INTEL XEON 2.5 GHZ (1333 Mhz) RAM: 10 GB RAM. PC2 5300. ARRAY: SmartArray P400, 8 SAS DISK, (RAID5+online spare) >How-To-Repeat: when boot with ACPI DISABLED MODE >Fix: unknown >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Wed Jan 14 07:55:48 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Wed Jan 14 07:55:55 2009 Subject: amd64/130536: not Message-ID: <200901141555.n0EFtjAs097164@freefall.freebsd.org> Synopsis: not State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Wed Jan 14 15:54:29 UTC 2009 State-Changed-Why: To submitter: Under amd64, ACPI is usually mandatory. Is there a reason you need to boot with ACPI disabled? Responsible-Changed-From-To: freebsd-amd64->gavin Responsible-Changed-By: gavin Responsible-Changed-When: Wed Jan 14 15:54:29 UTC 2009 Responsible-Changed-Why: Track http://www.freebsd.org/cgi/query-pr.cgi?pr=130536 From andrew.hotlab at hotmail.com Wed Jan 14 07:17:58 2009 From: andrew.hotlab at hotmail.com (Andrew Hotlab) Date: Wed Jan 14 08:33:37 2009 Subject: Cross compiling FreeBSD Message-ID: > From: andrew.hotlab@hotmail.com > To: freebsd-questions@freebsd.org > Subject: Builder for many architectures and releases > Date: Sat, 10 Jan 2009 02:37:37 +0000 > > [...] I looked for any documentation about setup a FreeBSD builder machine which will track sources and build binaries for all the hardware platform and OS releases I need to support in my network. I have found some interesting articles (http://www.onlamp.com/pub/a/bsd/2006/04/13/freebsd-build-system.html - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html), but nothing which actually addresses my needs. [...] > At this time, I've tried to build RELENG_7_1 for the i386 architecture using an amd64 machine (running RELENG_7_0 for amd64) then, exporting /usr/src and /usr/obj via NFS in read-only mode to target machines, I've experienced a lot of troubles trying to install both kernel and world, which made impossible for me to install FreeBSD on target i386 machines. Can anyone kindly confirm that it's a supported procedure to compile FreeBSD for a Tier1 architecture by using another Tier1-architecture machine? Maybe I didn't understood documentation or I'm missing some essential steps in the build process? Andrew P.S.: sorry for this cross-posting, but I don't have a clear understand about what list best suits my question! _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx From peterjeremy at optushome.com.au Wed Jan 14 13:16:29 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Wed Jan 14 13:16:36 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: <20090114211616.GC16116@server.vk2pj.dyndns.org> [Please wrap your lines before 80 columns] On 2009-Jan-14 15:06:06 +0000, Andrew Hotlab wrote: >At this time, I've tried to build RELENG_7_1 for the i386 >architecture using an amd64 machine (running RELENG_7_0 for amd64) >then, exporting /usr/src and /usr/obj via NFS in read-only mode to >target machines, This won't work because install{world,kernel} uses programs (under /usr/obj) that were built to run on the build system (amd64 in your case) and so won't run on the target (i386) system. The supported approach is to NFS mount the target machines onto the build machine and run "make DESTDIR=/mount/point install{world,kernel}" on the build machine. Note that this will report errors since NFS cannot handle UFS flags - you will need to manually remove/add schg flags. -- 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/20090114/30d8b4d8/attachment.pgp From andrew-freebsd at areilly.bpc-users.org Wed Jan 14 20:05:25 2009 From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly) Date: Wed Jan 14 20:05:33 2009 Subject: Cross compiling FreeBSD In-Reply-To: <20090114211616.GC16116@server.vk2pj.dyndns.org> References: <20090114211616.GC16116@server.vk2pj.dyndns.org> Message-ID: <20090115031847.GA52343@duncan.reilly.home> On Thu, Jan 15, 2009 at 08:16:17AM +1100, Peter Jeremy wrote: > This won't work because install{world,kernel} uses programs (under > /usr/obj) that were built to run on the build system (amd64 in > your case) and so won't run on the target (i386) system. > > The supported approach is to NFS mount the target machines onto the > build machine and run "make DESTDIR=/mount/point install{world,kernel}" > on the build machine. Note that this will report errors since NFS > cannot handle UFS flags - you will need to manually remove/add schg flags. Is there any reason (apart from using more space on the build machine) not to install to a DESTDIR (not /) on the build machine, and then tar/pax/cpio that tree across to the client system? Presumably something like that must be done for the distribution builds that go into making the CD and DVD images. NetBSD has (had? it's been a while since I looked) a cool mechanism that allowed the whole tree to be built (and "installed" to a DESTDIR) without root permissions, using a variation on install that copied the file as the running user and recorded the intended user/group/mod/flags in an mtree file. Then a subsequent task created a tarball that contained the file contents and the mtree permissions, all as a non-root user. So you don't even need to muck about with root-over-nfs issues for deployment: just log into the client and untar the distribution over the network (as root). Very, very neat, IMO. I used to build embedded i386 NetBSD installations on my amd64 FreeBSD system that way without much in the way of trouble. Haven't had to do it for a while, though, so perhaps it's all changed. I wouldn't hate to discover that FreeBSD can do that too, though... Cheers, Andrew From brooks at freebsd.org Wed Jan 14 21:07:37 2009 From: brooks at freebsd.org (Brooks Davis) Date: Wed Jan 14 21:50:53 2009 Subject: Cross compiling FreeBSD In-Reply-To: <20090115031847.GA52343@duncan.reilly.home> References: <20090114211616.GC16116@server.vk2pj.dyndns.org> <20090115031847.GA52343@duncan.reilly.home> Message-ID: <20090115044309.GA72611@lor.one-eyed-alien.net> On Thu, Jan 15, 2009 at 02:18:47PM +1100, Andrew Reilly wrote: > On Thu, Jan 15, 2009 at 08:16:17AM +1100, Peter Jeremy wrote: > > This won't work because install{world,kernel} uses programs (under > > /usr/obj) that were built to run on the build system (amd64 in > > your case) and so won't run on the target (i386) system. > > > > The supported approach is to NFS mount the target machines onto the > > build machine and run "make DESTDIR=/mount/point install{world,kernel}" > > on the build machine. Note that this will report errors since NFS > > cannot handle UFS flags - you will need to manually remove/add schg flags. > > Is there any reason (apart from using more space on the build > machine) not to install to a DESTDIR (not /) on the build > machine, and then tar/pax/cpio that tree across to the client > system? Presumably something like that must be done for the > distribution builds that go into making the CD and DVD images. This should work just fine. I use installs to DESTDIR to build images to be run at NFS root file systems. > NetBSD has (had? it's been a while since I looked) a cool > mechanism that allowed the whole tree to be built (and > "installed" to a DESTDIR) without root permissions, using a > variation on install that copied the file as the running user > and recorded the intended user/group/mod/flags in an mtree file. > Then a subsequent task created a tarball that contained the file > contents and the mtree permissions, all as a non-root user. So > you don't even need to muck about with root-over-nfs issues for > deployment: just log into the client and untar the distribution > over the network (as root). Very, very neat, IMO. I used to > build embedded i386 NetBSD installations on my amd64 FreeBSD > system that way without much in the way of trouble. Haven't had > to do it for a while, though, so perhaps it's all changed. I > wouldn't hate to discover that FreeBSD can do that too, > though... We don't have this yet, but lots of people would like to see this (just not quite enough to do it yet :). -- Brooks -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20090115/545ce7e6/attachment.pgp From kib at FreeBSD.org Thu Jan 15 10:03:51 2009 From: kib at FreeBSD.org (kib@FreeBSD.org) Date: Thu Jan 15 10:45:15 2009 Subject: amd64/130526: fsbase issues for i386 processes running on 7.1-RELEASE/amd64 Message-ID: <200901151803.n0FI3o1I021685@freefall.freebsd.org> Synopsis: fsbase issues for i386 processes running on 7.1-RELEASE/amd64 State-Changed-From-To: open->analyzed State-Changed-By: kib State-Changed-When: Thu Jan 15 18:03:16 UTC 2009 State-Changed-Why: I have a patch for the issue. Responsible-Changed-From-To: freebsd-amd64->kib Responsible-Changed-By: kib Responsible-Changed-When: Thu Jan 15 18:03:16 UTC 2009 Responsible-Changed-Why: I have a patch for the issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=130526 From jhb at freebsd.org Thu Jan 15 14:47:39 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Jan 15 14:48:04 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: <200901051616.39069.jkim@FreeBSD.org> References: <200901051616.39069.jkim@FreeBSD.org> Message-ID: <200901151703.33608.jhb@freebsd.org> On Monday 05 January 2009 4:16:36 pm Jung-uk Kim wrote: > On Monday 05 January 2009 02:24 pm, Koen Smits wrote: > > Hello all, > > > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on > > my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. > > This CPU is fully 64bit capable. But, when I try to boot Disc1 from > > an IDE CD-ROM I get the error "cpu doesn't support long mode", > > which implies the CPU can't do 64bit, and booting halts asking for > > a kernel. > > The first thing I tried was running ubuntu 8.10 64bit. It installs > > and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also > > boots and installs normally! > > Any help on fixing this is much appreciated. > > See: > > http://svn.freebsd.org/viewvc/base?view=revision&revision=183667 > http://svn.freebsd.org/viewvc/base?view=revision&revision=183823 > > I am not sure removing Via CPU support was intentional, though. Definitely not. At the time the kernel didn't support the Via CPU either. It seems you have fixed both the loader and kernel since, however. -- John Baldwin From peterjeremy at optushome.com.au Thu Jan 15 15:09:55 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Jan 15 15:10:07 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: <20090114211616.GC16116@server.vk2pj.dyndns.org> Message-ID: <20090115230949.GD16116@server.vk2pj.dyndns.org> On 2009-Jan-15 01:12:03 +0000, Andrew Hotlab wrote: >Ok, so I think that in a production environment I should deploy one builder machine >for each target architecture I have to support on my network... I'm right? A single build machine can cross-build for multiple environments so you really only need one machine. >One last question: I would expect the same issues if I wish to to support many >FreeBSD releases running of one single type of architecture? (i.e.: both builder >and targets are amd64 machines, but I run RELENG_7 on the builder and >RELENG_6_4 and RELENG_7_1 on the targets) In general, backward compatibility is supported, so a world built on a RELENG_7 box should be able to be installed by a RELENG_7_1 target (though not by a RELENG_6_4 target). And you can run into he same problem with different i386 variants - if your build machine is built with (eg) P4 options than a generic world built by that box cannot be installed by (eg) a P2 due to instruction differences. -- 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/20090115/24337888/attachment.pgp From hartzell at alerce.com Thu Jan 15 22:33:06 2009 From: hartzell at alerce.com (George Hartzell) Date: Thu Jan 15 23:05:05 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: <200901151703.33608.jhb@freebsd.org> References: <200901051616.39069.jkim@FreeBSD.org> <200901151703.33608.jhb@freebsd.org> Message-ID: <18800.9179.709405.287763@almost.alerce.com> John Baldwin writes: > On Monday 05 January 2009 4:16:36 pm Jung-uk Kim wrote: > > On Monday 05 January 2009 02:24 pm, Koen Smits wrote: > > > Hello all, > > > > > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on > > > my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. > > > This CPU is fully 64bit capable. But, when I try to boot Disc1 from > > > an IDE CD-ROM I get the error "cpu doesn't support long mode", > > > which implies the CPU can't do 64bit, and booting halts asking for > > > a kernel. > > > The first thing I tried was running ubuntu 8.10 64bit. It installs > > > and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also > > > boots and installs normally! > > > Any help on fixing this is much appreciated. > > > > See: > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=183667 > > http://svn.freebsd.org/viewvc/base?view=revision&revision=183823 > > > > I am not sure removing Via CPU support was intentional, though. > > Definitely not. At the time the kernel didn't support the Via CPU either. It > seems you have fixed both the loader and kernel since, however. The fix to the loader has a comment about MFC'ing in a week, but there are a bunch of changes to support padlock, MSI, etc... that don't have any such directives. When there isn't an explicit MFC directive with the commit, what does that mean for plans to merge them back to -STABLE? Thanks, g. From gavin at FreeBSD.org Fri Jan 16 03:52:41 2009 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Fri Jan 16 03:52:48 2009 Subject: kern/128102: AsusRock 939N68PV-GLAN not recognized Message-ID: <200901161152.n0GBqedR061337@freefall.freebsd.org> Synopsis: AsusRock 939N68PV-GLAN not recognized State-Changed-From-To: feedback->closed State-Changed-By: gavin State-Changed-When: Fri Jan 16 11:50:41 UTC 2009 State-Changed-Why: Close, from private correspondance (23 Oct 2008), submitter now has this working. http://www.freebsd.org/cgi/query-pr.cgi?pr=128102 From yanefbsd at gmail.com Fri Jan 16 00:41:40 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 16 04:22:58 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's Message-ID: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> Hi amd64 and Hackers, Uh, I'm really confused why 1) this error (errno => ENOMEM) would occur when I have more than enough free memory (both on x86 and amd64) and 2) why strerror would segfault in the call to errx in the attached sourcefile on amd64 only. Not initializing len causes the second output sample (errno => 14, which is EFAULT). Any ideas? Please CC me if mailing on amd64@ as I'm not subscribed to the list. Thanks, -Garrett /* Program */ #include #include #include #include #include int main() { int mib[4]; size_t len; if (sysctlnametomib("kern.ipc.shmmax", mib, &len) != 0) { printf("Errno: %d\n", errno); errx(errno, "Error: %s", strerror(errno)); } printf("%lu\n", len); return 0; } # output for len preset to 0: [gcooper@optimus ~]$ ./test2 Errno: 12 test2: Segmentation fault: 11 (core dumped) [gcooper@optimus ~]$ uname -a FreeBSD optimus.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #4: Sun Jan 11 12:30:31 PST 2009 root@optimus.gateway.2wire.net:/usr/obj/usr/src/sys/OPTIMUS amd64 [gcooper@orangebox /usr/home/gcooper]$ ./test Errno: 12 test: Error: Cannot allocate memory [gcooper@orangebox /usr/home/gcooper]$ uname -a FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #4: Sat Jan 3 22:54:52 PST 2009 gcooper@orangebox.gateway.2wire.net:/usr/obj/usr/src/sys/ORANGEBOX i386 # output for len not preset to 0: [gcooper@optimus ~]$ ./test2 Errno: 14 test2: Segmentation fault: 11 (core dumped) From yanefbsd at gmail.com Fri Jan 16 00:44:30 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 16 04:23:11 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> Message-ID: <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> On Fri, Jan 16, 2009 at 12:41 AM, Garrett Cooper wrote: > Hi amd64 and Hackers, > Uh, I'm really confused why 1) this error (errno => ENOMEM) would > occur when I have more than enough free memory (both on x86 and amd64) > and 2) why strerror would segfault in the call to errx in the attached > sourcefile on amd64 only. Not initializing len causes the second > output sample (errno => 14, which is EFAULT). > Any ideas? > Please CC me if mailing on amd64@ as I'm not subscribed to the list. > Thanks, > -Garrett > > /* Program */ > #include > #include > #include > #include > #include > > int > main() { > > int mib[4]; > > size_t len; > > if (sysctlnametomib("kern.ipc.shmmax", mib, &len) != 0) { > printf("Errno: %d\n", errno); > errx(errno, "Error: %s", strerror(errno)); > } > > printf("%lu\n", len); > > return 0; > > } > > # output for len preset to 0: > [gcooper@optimus ~]$ ./test2 > Errno: 12 > test2: Segmentation fault: 11 (core dumped) > [gcooper@optimus ~]$ uname -a > FreeBSD optimus.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #4: > Sun Jan 11 12:30:31 PST 2009 > root@optimus.gateway.2wire.net:/usr/obj/usr/src/sys/OPTIMUS amd64 > > [gcooper@orangebox /usr/home/gcooper]$ ./test > Errno: 12 > test: Error: Cannot allocate memory > [gcooper@orangebox /usr/home/gcooper]$ uname -a > FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT > #4: Sat Jan 3 22:54:52 PST 2009 > gcooper@orangebox.gateway.2wire.net:/usr/obj/usr/src/sys/ORANGEBOX > i386 > > # output for len not preset to 0: > [gcooper@optimus ~]$ ./test2 > Errno: 14 > test2: Segmentation fault: 11 (core dumped) Almost forgot -- here are the actual values reported by sysctl(1), just for reference: [gcooper@optimus ~]$ sysctl kern.ipc.shmall kern.ipc.shmmin kern.ipc.shmmax kern.ipc.shmall: 8192 kern.ipc.shmmin: 1 kern.ipc.shmmax: 33554432 [gcooper@orangebox /usr/src/sys]$ sysctl kern.ipc.shmall kern.ipc.shmmin kern.ipc.shmmax kern.ipc.shmall: 8192 kern.ipc.shmmin: 1 kern.ipc.shmmax: 33554432 Thanks, -Garrett From yanefbsd at gmail.com Fri Jan 16 00:53:21 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 16 04:23:20 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> Message-ID: <7d6fde3d0901160053y22b2f9c9vb37d0f0621c2a7c9@mail.gmail.com> On Fri, Jan 16, 2009 at 12:47 AM, Jacques Fourie wrote: > > You need to initialize len to the number of entries in the mib array. > Try adding 'len = 4' before calling sysctlnametomib() and see if your > issues go away. Ok, that solution works (I think). So, problem 2 down. Now: what about the segfaulting strerror(3) call on amd64 ;\? -Garrett From maxim at macomnet.ru Fri Jan 16 00:55:22 2009 From: maxim at macomnet.ru (Maxim Konovalov) Date: Fri Jan 16 04:23:30 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> Message-ID: <20090116115448.A32187@mp2.macomnet.net> On Fri, 16 Jan 2009, 00:44-0800, Garrett Cooper wrote: > On Fri, Jan 16, 2009 at 12:41 AM, Garrett Cooper wrote: > > Hi amd64 and Hackers, > > Uh, I'm really confused why 1) this error (errno => ENOMEM) would > > occur when I have more than enough free memory (both on x86 and amd64) > > and 2) why strerror would segfault in the call to errx in the attached > > sourcefile on amd64 only. Not initializing len causes the second > > output sample (errno => 14, which is EFAULT). > > Any ideas? - size_t len; + size_t len = 4; -- Maxim Konovalov From jacques.fourie at gmail.com Fri Jan 16 00:57:50 2009 From: jacques.fourie at gmail.com (Jacques Fourie) Date: Fri Jan 16 04:23:41 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> Message-ID: On Fri, Jan 16, 2009 at 10:47 AM, Jacques Fourie wrote: > On Fri, Jan 16, 2009 at 10:44 AM, Garrett Cooper wrote: >> On Fri, Jan 16, 2009 at 12:41 AM, Garrett Cooper wrote: >>> Hi amd64 and Hackers, >>> Uh, I'm really confused why 1) this error (errno => ENOMEM) would >>> occur when I have more than enough free memory (both on x86 and amd64) >>> and 2) why strerror would segfault in the call to errx in the attached >>> sourcefile on amd64 only. Not initializing len causes the second >>> output sample (errno => 14, which is EFAULT). >>> Any ideas? >>> Please CC me if mailing on amd64@ as I'm not subscribed to the list. >>> Thanks, >>> -Garrett >>> >>> /* Program */ >>> #include >>> #include >>> #include >>> #include >>> #include >>> >>> int >>> main() { >>> >>> int mib[4]; >>> >>> size_t len; >>> >>> if (sysctlnametomib("kern.ipc.shmmax", mib, &len) != 0) { >>> printf("Errno: %d\n", errno); >>> errx(errno, "Error: %s", strerror(errno)); >>> } >>> >>> printf("%lu\n", len); >>> >>> return 0; >>> >>> } >>> >>> # output for len preset to 0: >>> [gcooper@optimus ~]$ ./test2 >>> Errno: 12 >>> test2: Segmentation fault: 11 (core dumped) >>> [gcooper@optimus ~]$ uname -a >>> FreeBSD optimus.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #4: >>> Sun Jan 11 12:30:31 PST 2009 >>> root@optimus.gateway.2wire.net:/usr/obj/usr/src/sys/OPTIMUS amd64 >>> >>> [gcooper@orangebox /usr/home/gcooper]$ ./test >>> Errno: 12 >>> test: Error: Cannot allocate memory >>> [gcooper@orangebox /usr/home/gcooper]$ uname -a >>> FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT >>> #4: Sat Jan 3 22:54:52 PST 2009 >>> gcooper@orangebox.gateway.2wire.net:/usr/obj/usr/src/sys/ORANGEBOX >>> i386 >>> >>> # output for len not preset to 0: >>> [gcooper@optimus ~]$ ./test2 >>> Errno: 14 >>> test2: Segmentation fault: 11 (core dumped) >> >> Almost forgot -- here are the actual values reported by sysctl(1), >> just for reference: >> >> [gcooper@optimus ~]$ sysctl kern.ipc.shmall kern.ipc.shmmin kern.ipc.shmmax >> kern.ipc.shmall: 8192 >> kern.ipc.shmmin: 1 >> kern.ipc.shmmax: 33554432 >> >> [gcooper@orangebox /usr/src/sys]$ sysctl kern.ipc.shmall >> kern.ipc.shmmin kern.ipc.shmmax >> kern.ipc.shmall: 8192 >> kern.ipc.shmmin: 1 >> kern.ipc.shmmax: 33554432 >> >> Thanks, >> -Garrett >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > > You need to initialize len to the number of entries in the mib array. > Try adding 'len = 4' before calling sysctlnametomib() and see if your > issues go away. > Sorry, I only scanned through the code without reading the whole message before replying :) Please ignore... From yanefbsd at gmail.com Fri Jan 16 00:59:00 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 16 04:23:56 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <49704C13.60505@gmx.de> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <49704AEC.3080709@gmx.de> <7d6fde3d0901160056y7c395cb1m4675a3957b85f33d@mail.gmail.com> <49704C13.60505@gmx.de> Message-ID: <7d6fde3d0901160058x785b0af7r741fc779eb537d5@mail.gmail.com> On Fri, Jan 16, 2009 at 12:57 AM, Christoph Mallon wrote: > Garrett Cooper schrieb: >> >> Good point. I modified the source to do that. >> Thanks, >> -Garrett > > You should reply to all so the discussion stays on the list. Yeah, that was a goofup on my part. Go-go Gmail web interface! -Garrett From jacques.fourie at gmail.com Fri Jan 16 01:15:36 2009 From: jacques.fourie at gmail.com (Jacques Fourie) Date: Fri Jan 16 04:24:16 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <7d6fde3d0901160044x4d7735cep16f032cd99dbc835@mail.gmail.com> Message-ID: On Fri, Jan 16, 2009 at 10:44 AM, Garrett Cooper wrote: > On Fri, Jan 16, 2009 at 12:41 AM, Garrett Cooper wrote: >> Hi amd64 and Hackers, >> Uh, I'm really confused why 1) this error (errno => ENOMEM) would >> occur when I have more than enough free memory (both on x86 and amd64) >> and 2) why strerror would segfault in the call to errx in the attached >> sourcefile on amd64 only. Not initializing len causes the second >> output sample (errno => 14, which is EFAULT). >> Any ideas? >> Please CC me if mailing on amd64@ as I'm not subscribed to the list. >> Thanks, >> -Garrett >> >> /* Program */ >> #include >> #include >> #include >> #include >> #include >> >> int >> main() { >> >> int mib[4]; >> >> size_t len; >> >> if (sysctlnametomib("kern.ipc.shmmax", mib, &len) != 0) { >> printf("Errno: %d\n", errno); >> errx(errno, "Error: %s", strerror(errno)); >> } >> >> printf("%lu\n", len); >> >> return 0; >> >> } >> >> # output for len preset to 0: >> [gcooper@optimus ~]$ ./test2 >> Errno: 12 >> test2: Segmentation fault: 11 (core dumped) >> [gcooper@optimus ~]$ uname -a >> FreeBSD optimus.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #4: >> Sun Jan 11 12:30:31 PST 2009 >> root@optimus.gateway.2wire.net:/usr/obj/usr/src/sys/OPTIMUS amd64 >> >> [gcooper@orangebox /usr/home/gcooper]$ ./test >> Errno: 12 >> test: Error: Cannot allocate memory >> [gcooper@orangebox /usr/home/gcooper]$ uname -a >> FreeBSD orangebox.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT >> #4: Sat Jan 3 22:54:52 PST 2009 >> gcooper@orangebox.gateway.2wire.net:/usr/obj/usr/src/sys/ORANGEBOX >> i386 >> >> # output for len not preset to 0: >> [gcooper@optimus ~]$ ./test2 >> Errno: 14 >> test2: Segmentation fault: 11 (core dumped) > > Almost forgot -- here are the actual values reported by sysctl(1), > just for reference: > > [gcooper@optimus ~]$ sysctl kern.ipc.shmall kern.ipc.shmmin kern.ipc.shmmax > kern.ipc.shmall: 8192 > kern.ipc.shmmin: 1 > kern.ipc.shmmax: 33554432 > > [gcooper@orangebox /usr/src/sys]$ sysctl kern.ipc.shmall > kern.ipc.shmmin kern.ipc.shmmax > kern.ipc.shmall: 8192 > kern.ipc.shmmin: 1 > kern.ipc.shmmax: 33554432 > > Thanks, > -Garrett > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > You need to initialize len to the number of entries in the mib array. Try adding 'len = 4' before calling sysctlnametomib() and see if your issues go away. From christoph.mallon at gmx.de Fri Jan 16 01:19:44 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Fri Jan 16 04:24:31 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> Message-ID: <49704AEC.3080709@gmx.de> Garrett Cooper schrieb: > Hi amd64 and Hackers, > Uh, I'm really confused why 1) this error (errno => ENOMEM) would > occur when I have more than enough free memory (both on x86 and amd64) > and 2) why strerror would segfault in the call to errx in the attached > sourcefile on amd64 only. Not initializing len causes the second > output sample (errno => 14, which is EFAULT). > Any ideas? > Please CC me if mailing on amd64@ as I'm not subscribed to the list. > Thanks, > -Garrett len is not uninitialised. This leads to undefined behaviour. Anything can happen. Probably the syscall overwrites parts of the stack because len has some (random) high value. > /* Program */ > #include > #include > #include > #include > #include > > int > main() { > > int mib[4]; > > size_t len; > > if (sysctlnametomib("kern.ipc.shmmax", mib, &len) != 0) { > printf("Errno: %d\n", errno); > errx(errno, "Error: %s", strerror(errno)); The use of errno is wrong. printf might change errno. Store the errno into a local variable before you do any call, which might modify it. From yanefbsd at gmail.com Fri Jan 16 01:19:52 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 16 04:24:40 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160058x785b0af7r741fc779eb537d5@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <49704AEC.3080709@gmx.de> <7d6fde3d0901160056y7c395cb1m4675a3957b85f33d@mail.gmail.com> <49704C13.60505@gmx.de> <7d6fde3d0901160058x785b0af7r741fc779eb537d5@mail.gmail.com> Message-ID: <7d6fde3d0901160119u7ca9606dw55300cd279410ad2@mail.gmail.com> On Fri, Jan 16, 2009 at 12:58 AM, Garrett Cooper wrote: > On Fri, Jan 16, 2009 at 12:57 AM, Christoph Mallon > wrote: >> Garrett Cooper schrieb: >>> >>> Good point. I modified the source to do that. >>> Thanks, >>> -Garrett >> >> You should reply to all so the discussion stays on the list. > > Yeah, that was a goofup on my part. Go-go Gmail web interface! > -Garrett Hmmm... looks like the strerror issue it could be a serious bug: #include #include #include int main() { struct stat sb; int o_errno; if (stat("/some/file/that/doesn't/exist", &sb) != 0) { o_errno = errno; printf("Errno: %d\n", errno); err(errno, "%s", strerror(o_errno)); } return 0; } [gcooper@optimus ~]$ ./badfile Errno: 2 badfile: Segmentation fault: 11 (core dumped) I rebuilt my kernel and installed it, and I rebuilt world, but haven't installed it yet though, so let me reboot the amd64 machine and see what happens (may be a mismatched ABI issue)... Cheers, -Garrett From christoph.mallon at gmx.de Fri Jan 16 01:38:21 2009 From: christoph.mallon at gmx.de (Christoph Mallon) Date: Fri Jan 16 04:24:51 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160119u7ca9606dw55300cd279410ad2@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <49704AEC.3080709@gmx.de> <7d6fde3d0901160056y7c395cb1m4675a3957b85f33d@mail.gmail.com> <49704C13.60505@gmx.de> <7d6fde3d0901160058x785b0af7r741fc779eb537d5@mail.gmail.com> <7d6fde3d0901160119u7ca9606dw55300cd279410ad2@mail.gmail.com> Message-ID: <4970558A.1010705@gmx.de> Garrett Cooper schrieb: > On Fri, Jan 16, 2009 at 12:58 AM, Garrett Cooper wrote: >> On Fri, Jan 16, 2009 at 12:57 AM, Christoph Mallon >> wrote: >>> Garrett Cooper schrieb: >>>> Good point. I modified the source to do that. >>>> Thanks, >>>> -Garrett >>> You should reply to all so the discussion stays on the list. >> Yeah, that was a goofup on my part. Go-go Gmail web interface! >> -Garrett > > Hmmm... looks like the strerror issue it could be a serious bug: > > #include > #include > #include > > int > main() > { > > struct stat sb; > > int o_errno; > > if (stat("/some/file/that/doesn't/exist", &sb) != 0) { > o_errno = errno; > printf("Errno: %d\n", errno); > err(errno, "%s", strerror(o_errno)); You are still using the wrong errno. Also err() itself prints the error string using strerror(). There might be some interference when the result of one call to strerror() (your call) is used after another call to strerror() (err() internally). I doubt there is a bug in the library, otherwise we would see many bugreports of segfaults on AMD64. From ck-lists at cksoft.de Fri Jan 16 01:50:17 2009 From: ck-lists at cksoft.de (Christian Kratzer) Date: Fri Jan 16 04:25:01 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: Hi, On Wed, 14 Jan 2009, Andrew Hotlab wrote: > >> From: andrew.hotlab@hotmail.com >> To: freebsd-questions@freebsd.org >> Subject: Builder for many architectures and releases >> Date: Sat, 10 Jan 2009 02:37:37 +0000 >> >> [...] I looked for any documentation about setup a FreeBSD builder machine which will track sources and build binaries for all the hardware platform and OS releases I need to support in my network. I have found some interesting articles (http://www.onlamp.com/pub/a/bsd/2006/04/13/freebsd-build-system.html - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html), but nothing which actually addresses my needs. [...] >> > > At this time, I've tried to build RELENG_7_1 for the i386 architecture using an amd64 machine (running RELENG_7_0 for amd64) then, exporting /usr/src and /usr/obj via NFS in read-only mode to target machines, I've experienced a lot of troubles trying to install both kernel and world, which made impossible for me to install FreeBSD on target i386 machines. > Can anyone kindly confirm that it's a supported procedure to compile FreeBSD for a Tier1 architecture by using another Tier1-architecture machine? Maybe I didn't understood documentation or I'm missing some essential steps in the build process? as you already found out this does not work as the crossbuild process will build the native host tools in /usr/obj and the target system binaries in /usr/obj/i386. On recent RELENG_7 or HEAD machines you should be able to build in an i386 chroot. This would produce a clean /usr/obj you can copy to your i386 machines and install from there. The hack to enable building in an i386 chroot is to set UNAME_m and UNAME_p to i386. I use following in the chroots .cshrc setenv UNAME_m i386 setenv UNAME_p i386 This will avoid any crossbuild magic and you will be able to build as if on an i386 machine. This of course only works for the amd64, i386 combination. Greetings Christian -- Christian Kratzer CK Software GmbH Email: ck@cksoft.de Schwarzwaldstr. 31 Phone: +49 7452 889 135 D-71131 Jettingen Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer From andrew.hotlab at hotmail.com Fri Jan 16 02:24:47 2009 From: andrew.hotlab at hotmail.com (Andrew Hotlab) Date: Fri Jan 16 04:25:11 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: > Date: Fri, 16 Jan 2009 10:32:39 +0100 > From: ck-lists@cksoft.de > > On Wed, 14 Jan 2009, Andrew Hotlab wrote: > >> At this time, I've tried to build RELENG_7_1 for the i386 architecture using an amd64 >> machine (running RELENG_7_0 for amd64) then, exporting /usr/src and /usr/obj via >> NFS in read-only mode to target machines, I've experienced a lot of troubles trying to >> install both kernel and world, which made impossible for me to install FreeBSD on >> target i386 machines. >> Can anyone kindly confirm that it's a supported procedure to compile FreeBSD for >> a Tier1 architecture by using another Tier1-architecture machine? Maybe I didn't >> understood documentation or I'm missing some essential steps in the build process? > > as you already found out this does not work as the crossbuild process > will build the native host tools in /usr/obj and the target system > binaries in /usr/obj/i386. > > On recent RELENG_7 or HEAD machines you should be able to build > in an i386 chroot. This would produce a clean /usr/obj you > can copy to your i386 machines and install from there. > Sorry for my stupid question: I'll do the right thing if I'll build an i386 jail chroot/jail on the amd64 builder host with the following commands? (grabbed from the FreeBSD Handbook) # cd /usr/src # make buildworld TARGET=i386 # make installworld TARGET=i386 DESTDIR=/path-to-jail # cd etc/ # make distribution DESTDIR=/path-to-jail # mount -t devfs devfs /path-to-jail/dev > The hack to enable building in an i386 chroot is to set UNAME_m > and UNAME_p to i386. I use following in the chroots .cshrc > > setenv UNAME_m i386 > setenv UNAME_p i386 > > This will avoid any crossbuild magic and you will be able to build > as if on an i386 machine. > > This of course only works for the amd64, i386 combination. Wonderful, I'll try this as soon as possible. Thank you! _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx From ck-lists at cksoft.de Fri Jan 16 02:57:03 2009 From: ck-lists at cksoft.de (Christian Kratzer) Date: Fri Jan 16 04:25:18 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: Hi, On Fri, 16 Jan 2009, Andrew Hotlab wrote: > Sorry for my stupid question: I'll do the right thing if I'll build an i386 jail chroot/jail on the > amd64 builder host with the following commands? (grabbed from the FreeBSD Handbook) > # cd /usr/src > # make buildworld TARGET=i386 > # make installworld TARGET=i386 DESTDIR=/path-to-jail > # cd etc/ > # make distribution DESTDIR=/path-to-jail > # mount -t devfs devfs /path-to-jail/dev yes that should do it but I think you can skip the cd etc/ part. make distribution should work from /usr/src >> The hack to enable building in an i386 chroot is to set UNAME_m >> and UNAME_p to i386. I use following in the chroots .cshrc >> >> setenv UNAME_m i386 >> setenv UNAME_p i386 >> >> This will avoid any crossbuild magic and you will be able to build >> as if on an i386 machine. >> >> This of course only works for the amd64, i386 combination. > Wonderful, I'll try this as soon as possible. Thank you! let us know if it works out. Greetings Christian -- Christian Kratzer CK Software GmbH Email: ck@cksoft.de Schwarzwaldstr. 31 Phone: +49 7452 889 135 D-71131 Jettingen Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer From jhb at freebsd.org Fri Jan 16 07:28:17 2009 From: jhb at freebsd.org (John Baldwin) Date: Fri Jan 16 07:28:23 2009 Subject: Via Nano CPU: Can boot 7.0-RELEASE-amd64, can't boot 7.1-RELEASE-amd64: "cpu doesn't support long mode" In-Reply-To: <18800.9179.709405.287763@almost.alerce.com> References: <200901151703.33608.jhb@freebsd.org> <18800.9179.709405.287763@almost.alerce.com> Message-ID: <200901160928.16069.jhb@freebsd.org> On Friday 16 January 2009 1:06:19 am George Hartzell wrote: > John Baldwin writes: > > On Monday 05 January 2009 4:16:36 pm Jung-uk Kim wrote: > > > On Monday 05 January 2009 02:24 pm, Koen Smits wrote: > > > > Hello all, > > > > > > > > I have some problems getting FreeBSD 7.1-RELEASE amd64 to boot on > > > > my VIA VB8001, which is a mini-ITX board with the new VIA Nano CPU. > > > > This CPU is fully 64bit capable. But, when I try to boot Disc1 from > > > > an IDE CD-ROM I get the error "cpu doesn't support long mode", > > > > which implies the CPU can't do 64bit, and booting halts asking for > > > > a kernel. > > > > The first thing I tried was running ubuntu 8.10 64bit. It installs > > > > and runs fine. And, trying FreeBSD 7.0-RELEASE Disc1 amd64 also > > > > boots and installs normally! > > > > Any help on fixing this is much appreciated. > > > > > > See: > > > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=183667 > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=183823 > > > > > > I am not sure removing Via CPU support was intentional, though. > > > > Definitely not. At the time the kernel didn't support the Via CPU either. It > > seems you have fixed both the loader and kernel since, however. > > The fix to the loader has a comment about MFC'ing in a week, but there > are a bunch of changes to support padlock, MSI, etc... that don't have > any such directives. > > When there isn't an explicit MFC directive with the commit, what does > that mean for plans to merge them back to -STABLE? Nothing, sometimes a developer forgets them, or sometimes they will key off one reminder to merge an entire set of related commits. And sometimes we decide not to merge something we set a reminder for. -- John Baldwin From andrew.hotlab at hotmail.com Fri Jan 16 17:25:57 2009 From: andrew.hotlab at hotmail.com (Andrew Hotlab) Date: Fri Jan 16 17:52:47 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: > Date: Fri, 16 Jan 2009 11:56:55 +0100 > From: ck-lists@cksoft.de > > On Fri, 16 Jan 2009, Andrew Hotlab wrote: > >> Sorry for my stupid question: I'll do the right thing if I'll build an i386 jail chroot/jail on the >> amd64 builder host with the following commands? (grabbed from the FreeBSD Handbook) >> # cd /usr/src >> # make buildworld TARGET=i386 >> # make installworld TARGET=i386 DESTDIR=/path-to-jail >> # cd etc/ >> # make distribution DESTDIR=/path-to-jail >> # mount -t devfs devfs /path-to-jail/dev > > yes that should do it but I think you can skip the cd etc/ part. > make distribution should work from /usr/src > >>> The hack to enable building in an i386 chroot is to set UNAME_m >>> and UNAME_p to i386. I use following in the chroots .cshrc >>> [...] >>> This of course only works for the amd64, i386 combination. >> Wonderful, I'll try this as soon as possible. Thank you! > > let us know if it works out. I've build and exported RELENG_7_0 into an i386 jail running on amd64 hardware, then I mounted sources and binaries on a RELENG_6_4/i386 machine and I have been able to successfully upgrade without any trouble!! (only some warnings were displayed installing the kernel, but that's a correct behaviour of the upgrade procedure, as pointed out in this post: http://lists.freebsd.org/pipermail/freebsd-current/2005-November/057963.html) Thank you so much, Christian! I'm thinking that it would be a great thing to prepare some materials explaining the methods for maintaining a managed FreeBSD infrastructure in a corporate production environment. A lot of sysadmins are afraid that they'll have to spend so much time in software management tasks if they put FreeBSD in production for business applications, but it seems that only a little of knowledge is required to manage such and environment obtaining a good TCO. At present time I'm too much engaged with a lot of projects to be able to produce any docs, but I'll surely advocate FreeBSD in such business scenarios! _________________________________________________________________ More than messages?check out the rest of the Windows Live?. http://www.microsoft.com/windows/windowslive/ From des at des.no Sat Jan 17 05:40:14 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Sat Jan 17 05:40:21 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> (Garrett Cooper's message of "Fri, 16 Jan 2009 00:41:37 -0800") References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> Message-ID: <86wscuyska.fsf@ds4.des.no> Garrett Cooper writes: > #include > #include > #include > #include > #include You should always put your sys includes before your non-sys includes, and in any case, should always come first. > printf("Errno: %d\n", errno); > errx(errno, "Error: %s", strerror(errno)); In addition to what everybody else said, errno is not an appropriate value for errx's first argument. Use 1 or EXIT_FAILURE (or one of the macros defined in , but I wouldn't recommend it). Also, you probably want to use err(), not errx(), and *always* compile with -Wall -Wextra, and unless you're going to run gdb on your program, -O2 (which enables additional code analysis) DES -- Dag-Erling Sm?rgrav - des@des.no From mbsd at pacbell.net Sat Jan 17 14:16:29 2009 From: mbsd at pacbell.net (=?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?=) Date: Sat Jan 17 14:16:42 2009 Subject: Confused by segfault with legitimate call to strerror(3) on amd64 / sysctl(3) setting `odd' errno's In-Reply-To: <7d6fde3d0901160119u7ca9606dw55300cd279410ad2@mail.gmail.com> References: <7d6fde3d0901160041n55466290l55f737d274a40895@mail.gmail.com> <49704AEC.3080709@gmx.de> <7d6fde3d0901160056y7c395cb1m4675a3957b85f33d@mail.gmail.com> <49704C13.60505@gmx.de> <7d6fde3d0901160058x785b0af7r741fc779eb537d5@mail.gmail.com> <7d6fde3d0901160119u7ca9606dw55300cd279410ad2@mail.gmail.com> Message-ID: <20090117140506.A2568@antec.home> Hi Garrett, On Fri, 16 Jan 2009, Garrett Cooper wrote: > On Fri, Jan 16, 2009 at 12:58 AM, Garrett Cooper wrote: >> On Fri, Jan 16, 2009 at 12:57 AM, Christoph Mallon >> wrote: >>> Garrett Cooper schrieb: >>>> >>>> Good point. I modified the source to do that. >>>> Thanks, >>>> -Garrett >>> >>> You should reply to all so the discussion stays on the list. >> >> Yeah, that was a goofup on my part. Go-go Gmail web interface! >> -Garrett > > Hmmm... looks like the strerror issue it could be a serious bug: Add #include . Without it you don't get the strerror() prototype, so the return value defaults to an int. Thus the compiler will truncate the pointer value to junk. The crash happens when formatting the output. Compile with -Wall and pay attention to warnings (or use -Werror) to catch these things. $.02, /Mikko > > #include > #include > #include > > int > main() > { > > struct stat sb; > > int o_errno; > > if (stat("/some/file/that/doesn't/exist", &sb) != 0) { > o_errno = errno; > printf("Errno: %d\n", errno); > err(errno, "%s", strerror(o_errno)); > } > > return 0; > > } > > [gcooper@optimus ~]$ ./badfile > Errno: 2 > badfile: Segmentation fault: 11 (core dumped) > > I rebuilt my kernel and installed it, and I rebuilt world, but > haven't installed it yet though, so let me reboot the amd64 machine > and see what happens (may be a mismatched ABI issue)... > Cheers, > -Garrett > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From rjb at robertjbrown.com Sat Jan 17 16:10:03 2009 From: rjb at robertjbrown.com (Robert J. Brown) Date: Sat Jan 17 21:39:51 2009 Subject: amd64/129315: [boot] amd64 motherboard: Intel DG965WH motherboard compatibility with AMD64 Message-ID: <200901180010.n0I0A2OH051156@freefall.freebsd.org> The following reply was made to PR amd64/129315; it has been noted by GNATS. From: "Robert J. Brown" To: bug-followup@FreeBSD.org Cc: Subject: Re: amd64/129315: [boot] amd64 motherboard: Intel DG965WH motherboard compatibility with AMD64 Date: Sat, 17 Jan 2009 15:37:07 -0800 I tried this with 7.1-RELEASE and still have an issue but I do have an important update. At this point, I have just the bare board with a Core 2 Duo CPU and ATA hard drive set to cable select primary position. I attached a Plextor DVD/CD via USB. Nothing else is plugged in and I continue to get a reboot about 1/3 of the way through the kernel boot process and way before it mounts any disk partitions. It seems to indicate something about an interrupt before the reboot but it flashes by too quickly for me to see what the last message says. I disabled EVERY peripheral in the BIOS (sound, firewire, LAN, serial, parallel) and BOOM it works! The two other settings that I changed from the first post are the video mode was changed from DVMT to FIXED and I disabled "XD Technology" which is a link on the Security tab of the BIOS. I was able to boot the 7.1-RELEASE and install the OS to the hard drive. I then rebooted and turned on the peripherals one at a time to figure out what the problem was. I narrowed it down to the onboard LAN device. I now have everything else turned on except the onboard LAN and I can boot and have a stable system. Here are the BIOS settings that allow me to work properly (without LAN): Advanced->Boot Configuration Numlock On Max CPUID Value Limit Disable Display Setup Prompt On Advanced->Peripheral Configuration Serial Port Enable Parallel Port Disable (haven't tried this since I don't use it) Audio Enable On-board LAN Disable Onboard 1394 Enable Advanced->Drive Configuration ATA/IDE Mode Native Configure SATA at AHCI (IDE works too) SMART Enable Hard Disk Pre-Delay No Advanced->Floppy Configuration Floppy Disable Advanced->Video Configuration DVMT Mode Fixed IGD DVMT Memory 128MB IGD Aperture Size 128MB Primary Video Adaptor Auto Advanced->Fan Control Processor Zone Response Normal Processor Zone Damping Normal Automatic Fan Detection Disable Advanced->Chipset Configuration Memory Configuration SDRAM Control Manual CPC Override Disabled Memory Frequency 800MHz tCL 5 tRCD 5 tRP 5 tRASmin 15 PCI Express Config Compliance Test Pattern Disable PCI Latency Timer 32 HPET Disable Advanced->USB Configuration USB Ports Enable USB Legacy Enable Security Expansion Card Text Disable Chassis Intrusion Disable XD Technology Disable Intel Virtualization Technology Disable Power After Power Failure Power On Wake on LAN from S5 Power On Enhanced Intel SpeedStep Technology Enable Intel Quick Resume Techology Disable Wake system from S5 Disable I also updated to the latest 1754 BIOS release and still have the instant reboot if the LAN is enabled so this problem is true with the latest FreeBSD release and the latest BIOS for this board. The onboard LAN chip is an Intel 82566DC Gigabit Ethernet controller so I suspect this problem is related to that driver. Here is the dmesg output for the system where everything is running except onboard LAN: Copyright (c) 1992-2009 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-RELEASE #2: Sat Jan 17 14:31:36 PST 2009 root@:/usr/obj/usr/src/sys/SMOS0002 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (1868.54-MHz K8- class CPU) Origin = "GenuineIntel" Id = 0x6f6 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=0xe3bd AMD Features=0x20000800 AMD Features2=0x1 Cores per package: 2 usable memory = 3185475584 (3037 MB) avail memory = 3080007680 (2937 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x20f0-0x20f7 mem 0xd0200000-0xd02fffff,0xc0000000-0xcfffffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M drm0: on vgapci0 info: [drm] AGP at 0xc0000000 256MB info: [drm] Initialized i915 1.5.0 20060119 pci0: at device 3.0 (no driver attached) uhci0: port 0x20c0-0x20df irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x20a0-0x20bf irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xd0304c00-0xd0304fff irq 18 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: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 4 ports with 4 removable, self powered umass0: on uhub2 axe0: on uhub2 axe0: AX88772, bufsz 1536, boundary 64 miibus0: on axe0 ukphy0: PHY 16 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:50:b6:04:21:fc pcm0: mem 0xd0300000-0xd0303fff irq 22 at device 27.0 on pci0 pcm0: [ITHREAD] pcib1: at device 28.0 on pci0 pci1: on pcib1 pcib2: at device 28.1 on pci0 pci2: on pcib2 atapci0: port 0x1018-0x101f, 0x1024-0x1027,0x1010-0x1017,0x1020-0x1023,0x1000-0x100f mem 0xd0100000-0xd01001ff irq 17 at device 0.0 on pci2 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] pcib3: at device 28.2 on pci0 pci3: on pcib3 pcib4: at device 28.3 on pci0 pci4: on pcib4 pcib5: at device 28.4 on pci0 pci5: on pcib5 uhci2: port 0x2080-0x209f irq 23 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb3: on uhci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered uhci3: port 0x2060-0x207f irq 19 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0xd0304800-0xd0304bff irq 23 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: on ehci1 usb6: USB revision 2.0 uhub6: on usb6 uhub6: 6 ports with 6 removable, self powered pcib6: at device 30.0 on pci0 pci6: on pcib6 fwohci0: mem 0xd0004000-0xd00047ff, 0xd0000000-0xd0003fff irq 19 at device 3.0 on pci6 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:90:27:00:01:b4:c0:17 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:27:b4:c0:17 fwe0: Ethernet address: 02:90:27:b4:c0:17 fwip0: on firewire0 fwip0: Firewire address: 00:90:27:00:01:b4:c0:17 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xbe1cc000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0x20e8-0x20ef,0x20fc-0x20ff, 0x20e0-0x20e7,0x20f8-0x20fb,0x2020-0x203f mem 0xd0304000-0xd03047ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 6 ports detected ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] pci0: at device 31.3 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] cpu0: on acpi0 coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 orm0: at iomem 0xcb800-0xcc7ff on isa0 sc0: 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, defaultfirewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) to deny, logging disabled ad5: 152627MB at ata2-slave UDMA100 pcm0: pcm0: SMP: AP CPU #1 Launched! cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Trying to mount root from ufs:/dev/ad5s1a -- Robert J. Brown rjb@robertjbrown.com From fjo at ogris.de Sun Jan 18 05:40:04 2009 From: fjo at ogris.de (Felix J. Ogris) Date: Sun Jan 18 05:57:35 2009 Subject: amd64/130494: [btx] netbooting BTX fails on amd64 Message-ID: <200901181340.n0IDe3oL010391@freefall.freebsd.org> The following reply was made to PR amd64/130494; it has been noted by GNATS. From: "Felix J. Ogris" To: , Cc: Subject: Re: amd64/130494: [btx] netbooting BTX fails on amd64 Date: Sun, 18 Jan 2009 14:22:44 +0100 Hi, using BTX and /boot from 7.0-RELEASE-amd64-bootonly.iso, but /boot/kernel from 7.1-RELEASE-amd64-bootonly.iso works for me. Regards Felix From linimon at FreeBSD.org Sun Jan 18 15:25:02 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jan 18 15:50:44 2009 Subject: docs/128524: No geom documentation for loading gjournal(8) Message-ID: <200901182325.n0INP1wO096311@freefall.freebsd.org> Old Synopsis: No geom documentation for loading gjournal New Synopsis: No geom documentation for loading gjournal(8) Responsible-Changed-From-To: freebsd-amd64->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 18 23:24:27 UTC 2009 Responsible-Changed-Why: documentation issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=128524 From linimon at FreeBSD.org Sun Jan 18 15:25:51 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jan 18 15:50:50 2009 Subject: ports/128236: portsdb -Uu Indexing error Message-ID: <200901182325.n0INPoxP096366@freefall.freebsd.org> Synopsis: portsdb -Uu Indexing error State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Sun Jan 18 23:25:18 UTC 2009 State-Changed-Why: Is this still a problem? Responsible-Changed-From-To: freebsd-amd64->linimon Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 18 23:25:18 UTC 2009 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=128236 From linimon at FreeBSD.org Sun Jan 18 15:27:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jan 18 15:50:57 2009 Subject: amd64/125943: Serial Consoles do not work on amd64 freebsd Message-ID: <200901182327.n0INR7Sg096462@freefall.freebsd.org> Synopsis: Serial Consoles do not work on amd64 freebsd State-Changed-From-To: feedback->closed State-Changed-By: linimon State-Changed-When: Sun Jan 18 23:26:24 UTC 2009 State-Changed-Why: Feedback timeout (> 4 months). fwiw, I am currently able to use serial console on several machines in the package building cluster. http://www.freebsd.org/cgi/query-pr.cgi?pr=125943 From bugmaster at FreeBSD.org Mon Jan 19 03:06:55 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 19 04:25:16 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200901191106.n0JB6sZA062893@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/130494 amd64 [btx] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute 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/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127787 amd64 [lor] 3 lock LOR in recent CURRENT o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- 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 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/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 jhb at freebsd.org Tue Jan 20 11:44:02 2009 From: jhb at freebsd.org (John Baldwin) Date: Tue Jan 20 11:44:11 2009 Subject: amd64/130483: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server In-Reply-To: <200901130502.n0D5275X095567@www.freebsd.org> References: <200901130502.n0D5275X095567@www.freebsd.org> Message-ID: <200901201157.57956.jhb@freebsd.org> On Tuesday 13 January 2009 12:02:07 am Xiuchao Wu wrote: > > >Number: 130483 > >Category: amd64 > >Synopsis: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jan 13 05:10:01 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Xiuchao Wu > >Release: FreeBSD 7.0 > >Organization: > National University of Singapore > >Environment: > FreeBSD 7.0/7.1 Release > >Description: > Computer: Dell PowerEdge T300 Server > NICs: Myricom 10G-PCIE-8AL-C > OS: FreeBSD 7.0/7.1 Release > > After I rebuild the kernel (to include NIC driver "mxge") and reboot, kernel panic occurs and the computer is automatically rebooted. After contacting with engineers of Myricom, they suggest to disable message signaled interrupt (MSI) in /boot/loader.conf and these NICs can work now. > " > hw.pci.enable_msix=0 > hw.pci.enable_msi=0 > " > > However, MSI is really very important for high speed data transmission. Huge number of packets generate many interruptions. Considering that Fedora 9 works well on the same computer, it may be a bug of FreeBSD. Below is the screen when kernel panic occurs. > > > ...... > p4tcc3: on cpu3 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci3: on pcib1 > pcib2: at device 3.0 on pci0 > pci4: on pcib2 > pcib3: at device 4.0 on pci0 > pci5: on pcib3 > mxge0: mem 0xd8000000-0xd8ffffff, 0xdfa00000-0xdfafffff irq 16 at device 0.0 on pci5 > panic: nexus_add_irq: failed > ..... How many MSI messages is mxge0 attempting to add and how many other devices in your system are using MSI? Getting a full copy of a verbose dmesg would be most helpful. 'pciconf -lc' might also help answer the first question. -- John Baldwin From jhb at freebsd.org Tue Jan 20 11:50:03 2009 From: jhb at freebsd.org (John Baldwin) Date: Tue Jan 20 11:50:09 2009 Subject: amd64/130483: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server Message-ID: <200901201950.n0KJo2s2018968@freefall.freebsd.org> The following reply was made to PR amd64/130483; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: Xiuchao Wu , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/130483: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server Date: Tue, 20 Jan 2009 11:57:57 -0500 On Tuesday 13 January 2009 12:02:07 am Xiuchao Wu wrote: > > >Number: 130483 > >Category: amd64 > >Synopsis: MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Jan 13 05:10:01 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Xiuchao Wu > >Release: FreeBSD 7.0 > >Organization: > National University of Singapore > >Environment: > FreeBSD 7.0/7.1 Release > >Description: > Computer: Dell PowerEdge T300 Server > NICs: Myricom 10G-PCIE-8AL-C > OS: FreeBSD 7.0/7.1 Release > > After I rebuild the kernel (to include NIC driver "mxge") and reboot, kernel panic occurs and the computer is automatically rebooted. After contacting with engineers of Myricom, they suggest to disable message signaled interrupt (MSI) in /boot/loader.conf and these NICs can work now. > " > hw.pci.enable_msix=0 > hw.pci.enable_msi=0 > " > > However, MSI is really very important for high speed data transmission. Huge number of packets generate many interruptions. Considering that Fedora 9 works well on the same computer, it may be a bug of FreeBSD. Below is the screen when kernel panic occurs. > > > ...... > p4tcc3: on cpu3 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci3: on pcib1 > pcib2: at device 3.0 on pci0 > pci4: on pcib2 > pcib3: at device 4.0 on pci0 > pci5: on pcib3 > mxge0: mem 0xd8000000-0xd8ffffff, 0xdfa00000-0xdfafffff irq 16 at device 0.0 on pci5 > panic: nexus_add_irq: failed > ..... How many MSI messages is mxge0 attempting to add and how many other devices in your system are using MSI? Getting a full copy of a verbose dmesg would be most helpful. 'pciconf -lc' might also help answer the first question. -- John Baldwin From y2kwill2000 at yahoo.com.tw Wed Jan 21 04:00:09 2009 From: y2kwill2000 at yahoo.com.tw (wei guo jheng) Date: Wed Jan 21 04:31:58 2009 Subject: amd64/130817: FreeBSD does not support HP DL160G5 Message-ID: <200901211153.n0LBr7Ml052103@www.freebsd.org> >Number: 130817 >Category: amd64 >Synopsis: FreeBSD does not support HP DL160G5 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 21 12:00:08 UTC 2009 >Closed-Date: >Last-Modified: >Originator: wei guo jheng >Release: 6.3，6.4 ，7.1 all have tried >Organization: >Environment: The hardware scanning was unable to pass let alone, therefore was unable to install FreeBSD to carry out uname - a >Description: FreeBSD 6.3 and 6.4 for amd64 installs the install hardware scanning card on HP DL160G5 Server in acpi-button0: ON ACPI0 will not move，But FreeBSD 7.1 are scans p4tcc7: on cpu7 will not move >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From tinderbox at freebsd.org Wed Jan 21 12:49:37 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Jan 21 12:49:50 2009 Subject: [releng_6 tinderbox] failure on amd64/amd64 Message-ID: <20090121204930.C4437241BA@freebsd-legacy.sentex.ca> TB --- 2009-01-21 19:22:12 - tinderbox 2.6 running on freebsd-legacy.sentex.ca TB --- 2009-01-21 19:22:12 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2009-01-21 19:22:12 - cleaning the object tree TB --- 2009-01-21 19:23:08 - cvsupping the source tree TB --- 2009-01-21 19:23:08 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2009-01-21 19:23:19 - building world TB --- 2009-01-21 19:23:19 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 19:23:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 19:23:19 - TARGET=amd64 TB --- 2009-01-21 19:23:19 - TARGET_ARCH=amd64 TB --- 2009-01-21 19:23:19 - TZ=UTC TB --- 2009-01-21 19:23:19 - __MAKE_CONF=/dev/null TB --- 2009-01-21 19:23:19 - cd /src TB --- 2009-01-21 19:23:19 - /usr/bin/make -B buildworld >>> 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 TB --- 2009-01-21 20:41:11 - generating LINT kernel config TB --- 2009-01-21 20:41:11 - cd /src/sys/amd64/conf TB --- 2009-01-21 20:41:11 - /usr/bin/make -B LINT TB --- 2009-01-21 20:41:12 - building LINT kernel TB --- 2009-01-21 20:41:12 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-21 20:41:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-21 20:41:12 - TARGET=amd64 TB --- 2009-01-21 20:41:12 - TARGET_ARCH=amd64 TB --- 2009-01-21 20:41:12 - TZ=UTC TB --- 2009-01-21 20:41:12 - __MAKE_CONF=/dev/null TB --- 2009-01-21 20:41:12 - cd /src TB --- 2009-01-21 20:41:12 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Jan 21 20:41:12 UTC 2009 >>> 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 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_lookup.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_mount.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_subr.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/dev/ath -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/em -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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/kern/vfs_syscalls.c /src/sys/kern/vfs_syscalls.c: In function `kern_getdirentries': /src/sys/kern/vfs_syscalls.c:3715: error: `uap' undeclared (first use in this function) /src/sys/kern/vfs_syscalls.c:3715: error: (Each undeclared identifier is reported only once /src/sys/kern/vfs_syscalls.c:3715: error: for each function it appears in.) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-21 20:49:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-21 20:49:30 - ERROR: failed to build lint kernel TB --- 2009-01-21 20:49:30 - 4108.22 user 534.38 system 5237.80 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From tinderbox at freebsd.org Wed Jan 21 21:45:07 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Jan 21 21:45:23 2009 Subject: [releng_7 tinderbox] failure on amd64/amd64 Message-ID: <20090122054503.11F131B5060@freebsd-stable.sentex.ca> TB --- 2009-01-22 04:06:26 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 04:06:26 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-01-22 04:06:26 - cleaning the object tree TB --- 2009-01-22 04:06:46 - cvsupping the source tree TB --- 2009-01-22 04:06:46 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-01-22 04:06:56 - building world TB --- 2009-01-22 04:06:56 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 04:06:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 04:06:56 - TARGET=amd64 TB --- 2009-01-22 04:06:56 - TARGET_ARCH=amd64 TB --- 2009-01-22 04:06:56 - TZ=UTC TB --- 2009-01-22 04:06:56 - __MAKE_CONF=/dev/null TB --- 2009-01-22 04:06:56 - cd /src TB --- 2009-01-22 04:06:56 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 04:06:57 UTC 2009 >>> 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 Thu Jan 22 05:36:38 UTC 2009 TB --- 2009-01-22 05:36:38 - generating LINT kernel config TB --- 2009-01-22 05:36:38 - cd /src/sys/amd64/conf TB --- 2009-01-22 05:36:38 - /usr/bin/make -B LINT TB --- 2009-01-22 05:36:38 - building LINT kernel TB --- 2009-01-22 05:36:38 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 05:36:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 05:36:38 - TARGET=amd64 TB --- 2009-01-22 05:36:38 - TARGET_ARCH=amd64 TB --- 2009-01-22 05:36:38 - TZ=UTC TB --- 2009-01-22 05:36:38 - __MAKE_CONF=/dev/null TB --- 2009-01-22 05:36:38 - cd /src TB --- 2009-01-22 05:36:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 05:36:38 UTC 2009 >>> 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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhid.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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uhub.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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/uipaq.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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ukbd.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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/ulpt.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-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/dev/usb/umass.c /src/sys/dev/usb/umass.c:577: error: 'USB_PRODUCT_NETAC_ONLYDISK' undeclared here (not in a function) /src/sys/dev/usb/umass.c:613: error: 'USB_PRODUCT_ONSPEC_SDS_HOTFIND_D' undeclared here (not in a function) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 05:45:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 05:45:02 - ERROR: failed to build lint kernel TB --- 2009-01-22 05:45:02 - 4882.45 user 554.26 system 5916.19 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From dougb at FreeBSD.org Wed Jan 21 22:17:08 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Wed Jan 21 22:17:25 2009 Subject: Cross compiling FreeBSD In-Reply-To: References: Message-ID: <4978093A.5060504@FreeBSD.org> Andrew Hotlab wrote: > Sorry for my stupid question: I'll do the right thing if I'll build an i386 jail chroot/jail on the > amd64 builder host with the following commands? (grabbed from the FreeBSD Handbook) > # cd /usr/src > # make buildworld TARGET=i386 > # make installworld TARGET=i386 DESTDIR=/path-to-jail > # cd etc/ > # make distribution DESTDIR=/path-to-jail You can replace those last two lines with: mergemaster -i -A i386 -D /path-to-jail In previous incarnations mergemaster was less than completely effective *cough* in cross-build applications, but thanks to prodding from Sam and help from Ruslan it works now (where "now" means -current and 7-stable after the 7.1 release). hth, Doug -- This .signature sanitized for your protection From vsjcfm at gmail.com Thu Jan 22 01:30:03 2009 From: vsjcfm at gmail.com (Sayetsky Anton) Date: Thu Jan 22 04:18:59 2009 Subject: amd64/130864: Problem with copying files to a large partition Message-ID: <200901220928.n0M9SRMA094783@www.freebsd.org> >Number: 130864 >Category: amd64 >Synopsis: Problem with copying files to a large partition >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 22 09:30:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Sayetsky Anton >Release: FreeBSD-7.1-RELEASE-p2 amd64 >Organization: LDS >Environment: FreeBSD upload.lds.net.ua 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Thu Jan 22 10:41:11 EET 2009 jason@upload.lds.net.ua:/home/cvs/obj/home/cvs/src/sys/UPLOAD2 amd64 >Description: FreeBSD is hang when copiyng files (size between 10MiB and 1GiB) to a large partition (1TiB) less /var/run/dmesg.boot Copyright (c) 1992-2009 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-RELEASE-p2 #0: Thu Jan 22 10:41:11 EET 2009 jason@upload.lds.net.ua:/home/cvs/obj/home/cvs/src/sys/UPLOAD2 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz (2000.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 1055449088 (1006 MB) avail memory = 1016774656 (969 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3f4e0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0xe200-0xe207 mem 0xf3100000-0xf317ffff,0xe0000000-0xefffffff,0xf3000000-0xf30fffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7164k stolen memory agp0: aperture size is 256M uhci0: port 0xe600-0xe61f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe000-0xe01f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe100-0xe11f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xf3181000-0xf31813ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 28.4 on pci0 pci2: on pcib2 atapci0: port 0xc000-0xc007,0xc100-0xc103,0xc200-0xc207,0xc300-0xc303,0xc400-0xc40f irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] uhci3: port 0xe300-0xe31f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xe400-0xe41f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xe500-0xe51f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xf3180000-0xf31803ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb7: USB revision 2.0 uhub7: on usb7 uhub7: 6 ports with 6 removable, self powered pcib3: at device 30.0 on pci0 pci3: on pcib3 em0: port 0xd000-0xd03f mem 0xf2020000-0xf203ffff,0xf2000000-0xf201ffff irq 20 at device 0.0 on pci3 em0: [FILTER] em0: Ethernet address: 00:1b:21:0a:cd:8a isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xe700-0xe707,0xe800-0xe803,0xe900-0xe907,0xea00-0xea03,0xeb00-0xeb1f mem 0xf3182000-0xf31827ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.20 controller with 6 ports detected ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: [ITHREAD] ata8: on atapci1 ata8: [ITHREAD] pci0: at device 31.3 (no driver attached) 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: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] 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: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 cpu0: on acpi0 acpi_perf0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr a280a2806000a28 device_attach: est1 attach returned 6 p4tcc1: on cpu1 orm0: at iomem 0xcc000-0xccfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ad6: 381553MB at ata3-master SATA300 ad8: 953868MB at ata4-master SATA300 SMP: AP CPU #1 Launched! GEOM_JOURNAL: Journal 252456569: ad8 contains data. GEOM_JOURNAL: Journal 252456569: ad8 contains journal. GEOM_JOURNAL: Journal ad8 clean. Trying to mount root from ufs:/dev/ad6s1a em0: link state changed to UP upload# mount /dev/ad6s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad6s1d on /var (ufs, local, soft-updates) /dev/ad6s1e on /var/log (ufs, local, soft-updates) /dev/ad6s1f on /var/tmp (ufs, local, noatime, soft-updates) /dev/ad6s1g on /tmp (ufs, local, noatime, soft-updates) /dev/ad6s2d on /usr (ufs, local) /dev/ad6s2e on /usr/local (ufs, local, soft-updates) /dev/ad6s2f on /home (ufs, local, soft-updates) /dev/ad8.journal on /mnt/files (ufs, local, gjournal) upload# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad6s1a 629M 280M 299M 48% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad6s1d 15G 60M 13G 0% /var /dev/ad6s1e 2.9G 282K 2.7G 0% /var/log /dev/ad6s1f 1.9G 904K 1.8G 0% /var/tmp /dev/ad6s1g 1.9G 14K 1.8G 0% /tmp /dev/ad6s2d 678M 146M 477M 23% /usr /dev/ad6s2e 2.9G 303M 2.4G 11% /usr/local /dev/ad6s2f 334G 1.1G 306G 0% /home /dev/ad8.journal 900G 992M 872G 0% /mnt/files upload# cat /root/kernconf/UPLOAD2 | grep -v ^# cpu HAMMER ident UPLOAD2 options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD # Network Lock Manager options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing options SMP # Symmetric MultiProcessor Kernel device cpufreq device acpi device pci device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support device sc device agp # support several AGP chipsets device sio # 8250, 16[45]50 based serial ports device uart # Generic UART driver device em # Intel PRO/1000 Gigabit Ethernet Family device loop # Network loopback device random # Entropy device device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device bpf # Berkeley packet filter device uhci # UHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse options SC_NORM_ATTR=(FG_LIGHTGREY|BG_BLACK) options SC_NORM_REV_ATTR=(FG_BLACK|BG_LIGHTGREY) options SC_KERNEL_CONS_ATTR=(FG_GREEN|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_YELLOW|BG_GREEN) options NULLFS options GEOM_JOURNAL >How-To-Repeat: Simply start copying files to a large partition. FreeBSD hangs after 3-5 minutes, and no kernel panic messages are displayed. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From danny at cs.huji.ac.il Thu Jan 22 06:00:21 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Thu Jan 22 06:01:41 2009 Subject: amd64/130885: sockstat on amd64 does not work Message-ID: >Number: 130885 >Category: amd64 >Synopsis: sockstat on amd64 does not work >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: Thu Jan 22 14:00:15 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Danny Braniss >Release: FreeBSD 7.1-STABLE amd64 >Organization: >Environment: System: FreeBSD dell-2950 7.1-STABLE FreeBSD 7.1-STABLE #36: Fri Jan 16 13:06:56 IST 2009 danny@sunfire:/r+d/obj/sunfire/r+d/7/sys/HUJI amd64 >Description: sockstat on amd64 does not work >How-To-Repeat: > sockstat sockstat: struct xtcpcb size mismatch sockstat: struct xinpcb size mismatch sockstat: struct xunpcb size mismatch sockstat: struct xunpcb size mismatch USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS >Fix: >Release-Note: >Audit-Trail: >Unformatted: From jhb at freebsd.org Thu Jan 22 07:41:49 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Jan 22 07:41:55 2009 Subject: amd64/130885: sockstat on amd64 does not work In-Reply-To: References: Message-ID: <200901220943.47023.jhb@freebsd.org> On Thursday 22 January 2009 8:21:48 am Danny Braniss wrote: > > >Number: 130885 > >Category: amd64 > >Synopsis: sockstat on amd64 does not work > >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: Thu Jan 22 14:00:15 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Danny Braniss > >Release: FreeBSD 7.1-STABLE amd64 > >Organization: > >Environment: > System: FreeBSD dell-2950 7.1-STABLE FreeBSD 7.1-STABLE #36: Fri Jan 16 13:06:56 IST 2009 danny@sunfire:/r+d/obj/sunfire/r+d/7/sys/HUJI amd64 > > > > >Description: > sockstat on amd64 does not work > >How-To-Repeat: > > sockstat > sockstat: struct xtcpcb size mismatch > sockstat: struct xinpcb size mismatch > sockstat: struct xunpcb size mismatch > sockstat: struct xunpcb size mismatch > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS Your kernel and world are out of sync. What was your previous kernel version? -- John Baldwin From jhb at freebsd.org Thu Jan 22 07:50:04 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Jan 22 07:50:16 2009 Subject: amd64/130885: sockstat on amd64 does not work Message-ID: <200901221550.n0MFo3IN083685@freefall.freebsd.org> The following reply was made to PR amd64/130885; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org, Danny Braniss Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/130885: sockstat on amd64 does not work Date: Thu, 22 Jan 2009 09:43:46 -0500 On Thursday 22 January 2009 8:21:48 am Danny Braniss wrote: > > >Number: 130885 > >Category: amd64 > >Synopsis: sockstat on amd64 does not work > >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: Thu Jan 22 14:00:15 UTC 2009 > >Closed-Date: > >Last-Modified: > >Originator: Danny Braniss > >Release: FreeBSD 7.1-STABLE amd64 > >Organization: > >Environment: > System: FreeBSD dell-2950 7.1-STABLE FreeBSD 7.1-STABLE #36: Fri Jan 16 13:06:56 IST 2009 danny@sunfire:/r+d/obj/sunfire/r+d/7/sys/HUJI amd64 > > > > >Description: > sockstat on amd64 does not work > >How-To-Repeat: > > sockstat > sockstat: struct xtcpcb size mismatch > sockstat: struct xinpcb size mismatch > sockstat: struct xunpcb size mismatch > sockstat: struct xunpcb size mismatch > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS Your kernel and world are out of sync. What was your previous kernel version? -- John Baldwin From linimon at FreeBSD.org Thu Jan 22 10:06:57 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Jan 22 10:14:37 2009 Subject: amd64/130885: sockstat(1) on amd64 does not work Message-ID: <200901221806.n0MI6uiU087955@freefall.freebsd.org> Old Synopsis: sockstat on amd64 does not work New Synopsis: sockstat(1) on amd64 does not work State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Thu Jan 22 18:06:21 UTC 2009 State-Changed-Why: Note that submitter has been asked for feedback. http://www.freebsd.org/cgi/query-pr.cgi?pr=130885 From tinderbox at freebsd.org Thu Jan 22 13:26:26 2009 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Jan 22 13:26:33 2009 Subject: [releng_7 tinderbox] failure on amd64/amd64 Message-ID: <20090122212619.1A5181B5060@freebsd-stable.sentex.ca> TB --- 2009-01-22 19:46:04 - tinderbox 2.6 running on freebsd-stable.sentex.ca TB --- 2009-01-22 19:46:04 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2009-01-22 19:46:04 - cleaning the object tree TB --- 2009-01-22 19:46:19 - cvsupping the source tree TB --- 2009-01-22 19:46:19 - /usr/bin/csup -z -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2009-01-22 19:46:28 - building world TB --- 2009-01-22 19:46:28 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 19:46:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 19:46:28 - TARGET=amd64 TB --- 2009-01-22 19:46:28 - TARGET_ARCH=amd64 TB --- 2009-01-22 19:46:28 - TZ=UTC TB --- 2009-01-22 19:46:28 - __MAKE_CONF=/dev/null TB --- 2009-01-22 19:46:28 - cd /src TB --- 2009-01-22 19:46:28 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 22 19:46:29 UTC 2009 >>> 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 Thu Jan 22 21:16:03 UTC 2009 TB --- 2009-01-22 21:16:03 - generating LINT kernel config TB --- 2009-01-22 21:16:03 - cd /src/sys/amd64/conf TB --- 2009-01-22 21:16:03 - /usr/bin/make -B LINT TB --- 2009-01-22 21:16:03 - building LINT kernel TB --- 2009-01-22 21:16:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-01-22 21:16:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-01-22 21:16:03 - TARGET=amd64 TB --- 2009-01-22 21:16:03 - TARGET_ARCH=amd64 TB --- 2009-01-22 21:16:03 - TZ=UTC TB --- 2009-01-22 21:16:03 - __MAKE_CONF=/dev/null TB --- 2009-01-22 21:16:03 - cd /src TB --- 2009-01-22 21:16:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jan 22 21:16:03 UTC 2009 >>> 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 [...] /src/sys/kern/vfs_aio.c:2633: error: dereferencing pointer to incomplete type /src/sys/kern/vfs_aio.c: In function 'freebsd32_olio_listio': /src/sys/kern/vfs_aio.c:2859: error: storage size of 'osig' isn't known cc1: warnings being treated as errors /src/sys/kern/vfs_aio.c:2859: warning: unused variable 'osig' /src/sys/kern/vfs_aio.c: In function 'freebsd32_lio_listio': /src/sys/kern/vfs_aio.c:2904: error: storage size of 'sig32' isn't known /src/sys/kern/vfs_aio.c:2904: warning: unused variable 'sig32' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-01-22 21:26:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-01-22 21:26:18 - ERROR: failed to build lint kernel TB --- 2009-01-22 21:26:18 - 4963.09 user 557.23 system 6014.45 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-amd64-amd64.full From danny at cs.huji.ac.il Fri Jan 23 07:00:05 2009 From: danny at cs.huji.ac.il (Danny Braniss) Date: Fri Jan 23 07:00:11 2009 Subject: amd64/130885: sockstat on amd64 does not work (fwd) Message-ID: <200901231500.n0NF03qB074458@freefall.freebsd.org> The following reply was made to PR amd64/130885; it has been noted by GNATS. From: Danny Braniss To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: amd64/130885: sockstat on amd64 does not work (fwd) Date: Fri, 23 Jan 2009 16:56:16 +0200 On Thursday 22 January 2009 10:50:52 am Danny Braniss wrote: > > On Thursday 22 January 2009 8:21:48 am Danny Braniss wrote: > > > > > > >Number: 130885 > > > >Category: amd64 > > > >Synopsis: sockstat on amd64 does not work > > > >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: Thu Jan 22 14:00:15 UTC 2009 > > > >Closed-Date: > > > >Last-Modified: > > > >Originator: Danny Braniss > > > >Release: FreeBSD 7.1-STABLE amd64 > > > >Organization: > > > >Environment: > > > System: FreeBSD dell-2950 7.1-STABLE FreeBSD 7.1-STABLE #36: Fri Jan 16 > > 13:06:56 IST 2009 danny@sunfire:/r+d/obj/sunfire/r+d/7/sys/HUJI amd64 > > > > > > > > > > > > >Description: > > > sockstat on amd64 does not work > > > >How-To-Repeat: > > > > sockstat > > > sockstat: struct xtcpcb size mismatch > > > sockstat: struct xinpcb size mismatch > > > sockstat: struct xunpcb size mismatch > > > sockstat: struct xunpcb size mismatch > > > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS > > > > Your kernel and world are out of sync. What was your previous kernel version? > > > 7.0, 7.1-pre, 7.1-rel, 7.1-stable > > I am using the same sources to compile for i386, and there it works fine. > (im synching via svn, so maybe/probably, something is out of sync) Hmm, the ABI shouldn't have broken for those structures in 7.x. -- John Baldwin From subscr1024 at mail.ru Fri Jan 23 10:36:18 2009 From: subscr1024 at mail.ru (Subscriber) Date: Fri Jan 23 10:36:25 2009 Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64] In-Reply-To: <20081212145015.GE2038@deviant.kiev.zoral.com.ua> References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com> <20061231003901.GA76688@slackbox.xs4all.nl> <20081212130631.GC2038@deviant.kiev.zoral.com.ua> <49427649.20006@lapo.it> <20081212145015.GE2038@deviant.kiev.zoral.com.ua> Message-ID: <4979D9F5.6020105@mail.ru> Hello, Kostik. I applied those patch to my 8C system about to or three weeks ago. But after applying patch I had xorg server became unstable. It was crashed occasionally with SIGBUS. Rebuilding xorg-server and all dependencies not made any effect. Can anybody know some info about this issue? Sorry for bad English. -- Cache Kostik Belousov ?????: > 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. From scott.gasch at gmail.com Fri Jan 23 23:00:41 2009 From: scott.gasch at gmail.com (Scott Gasch) Date: Sat Jan 24 02:21:38 2009 Subject: Problems with ata driver on current / Asus P5Q-E Message-ID: Hi, I've been running a 7.1-p1 (amd64) system and and seeing very high interrupt rates on irq19 which is shared between several devices. Over 60% of one core is used responding to interrupts. The machine also hangs frequently. irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... the consensus response to my last question was that "it's probably the ata driver". Today I tried building and booting a GENERIC current kernel and got another piece of information. The freebsd-current GENERIC kernel does not boot; shortly after probing the drives it says "Cannot setup DMA" several times on the console and hangs. This machine is an Asus P5Q-E... I believe it has two ATA controllers: a Marvell 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets generating interrupts that the driver doesn't understand and/or properly dismiss? Can it be put into a legacy mode that works? This machine has problems in 7.0, 7.1 and current... I'm running out of ideas. Thx, Scott From kostikbel at gmail.com Sat Jan 24 06:45:31 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Sat Jan 24 06:45:37 2009 Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64] In-Reply-To: <4979D9F5.6020105@mail.ru> References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com> <20061231003901.GA76688@slackbox.xs4all.nl> <20081212130631.GC2038@deviant.kiev.zoral.com.ua> <49427649.20006@lapo.it> <20081212145015.GE2038@deviant.kiev.zoral.com.ua> <4979D9F5.6020105@mail.ru> Message-ID: <20090124132823.GA6834@deviant.kiev.zoral.com.ua> On Fri, Jan 23, 2009 at 05:53:41PM +0300, Subscriber wrote: > Hello, Kostik. > > I applied those patch to my 8C system about to or three weeks ago. But > after applying patch I had xorg server became unstable. It was crashed > occasionally with SIGBUS. Rebuilding xorg-server and all dependencies not > made any effect. Can anybody know some info about this issue? What is "8C" system ? Eight-core ? First, what was the version of the patch ? All publically released patches are no longer applicable to the HEAD. The latest version is at http://people.freebsd.org/~kib/misc/amd64_ctx.3.patch Did you tried to run wine/i386 on the box ? To debug the issue with Xorg, I need to look at the instruction where the code faults. Specifically, please enable coredump from Xorg, load coredump in gdb (like gdb Xorg Xorg.core) and then info registers disassemble <%rip value> <%rip value>+0x10 Thanks for testing. -------------- 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/20090124/99baf8b6/attachment.pgp From oliver.pntr at gmail.com Sat Jan 24 08:20:44 2009 From: oliver.pntr at gmail.com (Oliver Pinter) Date: Sat Jan 24 08:20:53 2009 Subject: Problems with ata driver on current / Asus P5Q-E In-Reply-To: References: Message-ID: <6101e8c40901240749h106916adya7d6a8caee4ed155@mail.gmail.com> I have the same MB, and it running perfect, but I have only 3 SATA HDD + 1 SATA DVD-RW The ICH is in RAID mode. Attached my conf and dmesg Which version of BIOS use You? [snip] Southbridge - 6 x SATA 3Gb/s - Intel(R) Matrix Storage Technology with RAID 0, 1, 5, 10 support Marvell 88SE6121 - 1 x UltraDMA 133/100/66 for up to 2 PATA devices - 1 x External SATA 3Gb/s port (SATA On-the-Go) Silicon Image Sil5723 (Drive Xpert technology) - 2 x SATA 3Gb/s - Supports EZ Backup and Super Speed functions [snip] http://www.asus.com/products.aspx?l1=3&l2=11&l3=709&l4=0&model=2267&modelmenu=2 /* sorry for bad english */ On 1/24/09, Scott Gasch wrote: > Hi, > I've been running a 7.1-p1 (amd64) system and and seeing very high interrupt > rates on irq19 which is shared between several devices. Over 60% of one > core is used responding to interrupts. The machine also hangs frequently. > irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... > the consensus response to my last question was that "it's probably the ata > driver". > > Today I tried building and booting a GENERIC current kernel and got another > piece of information. The freebsd-current GENERIC kernel does not boot; > shortly after probing the drives it says "Cannot setup DMA" several times on > the console and hangs. > > This machine is an Asus P5Q-E... I believe it has two ATA controllers: > a Marvell > 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets generating > interrupts that the driver doesn't understand and/or properly dismiss? Can > it be put into a legacy mode that works? This machine has problems in 7.0, > 7.1 and current... I'm running out of ideas. > > Thx, > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From scott.gasch at gmail.com Sat Jan 24 15:03:52 2009 From: scott.gasch at gmail.com (scott.gasch@gmail.com) Date: Sat Jan 24 15:15:43 2009 Subject: Problems with ata driver on current / Asus P5Q-E In-Reply-To: <6101e8c40901240749h106916adya7d6a8caee4ed155@mail.gmail.com> Message-ID: <00163641792bd5eece046142843d@google.com> Hi Oliver, Thanks for the reply. I'm running bios version 02.61 American Megatrends Inc; it has never been updated. I just got the latest image (1703) from ASUS and will try flashing it. I don't have my controller set on RAID because I don't want hardware RAID... it's set on AHCI instead. Maybe this is the difference. Are you doing hardware RAID? I'm still looking over your config and dmesg, thanks for sending those. I'll report back if I figure anything out. Thx, Scott On Jan 24, 2009 7:49am, Oliver Pinter wrote: > I have the same MB, and it running perfect, but I have only 3 SATA HDD > > + 1 SATA DVD-RW > > > > The ICH is in RAID mode. > > > > Attached my conf and dmesg > > > > Which version of BIOS use You? > > > > [snip] > > Southbridge > > - 6 x SATA 3Gb/s > > - Intel(R) Matrix Storage Technology with RAID 0, 1, 5, 10 support > > Marvell 88SE6121 > > - 1 x UltraDMA 133/100/66 for up to 2 PATA devices > > - 1 x External SATA 3Gb/s port (SATA On-the-Go) > > Silicon Image Sil5723 (Drive Xpert technology) > > - 2 x SATA 3Gb/s > > - Supports EZ Backup and Super Speed functions > > [snip] > > > > http://www.asus.com/products.aspx?l1=3&l2=11&l3=709&l4=0&model=2267&modelmenu=2 > > > > /* sorry for bad english */ > > > > On 1/24/09, Scott Gasch scott.gasch@gmail.com> wrote: > > > Hi, > > > I've been running a 7.1-p1 (amd64) system and and seeing very high interrupt > > > rates on irq19 which is shared between several devices. Over 60% of one > > > core is used responding to interrupts. The machine also hangs frequently. > > > irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... > > > the consensus response to my last question was that "it's probably the ata > > > driver". > > > > > > Today I tried building and booting a GENERIC current kernel and got another > > > piece of information. The freebsd-current GENERIC kernel does not boot; > > > shortly after probing the drives it says "Cannot setup DMA" several times on > > > the console and hangs. > > > > > > This machine is an Asus P5Q-E... I believe it has two ATA controllers: > > > a Marvell > > > 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets generating > > > interrupts that the driver doesn't understand and/or properly dismiss? Can > > > it be put into a legacy mode that works? This machine has problems in 7.0, > > > 7.1 and current... I'm running out of ideas. > > > > > > Thx, > > > Scott > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > From subscr1024 at mail.ru Sun Jan 25 12:49:36 2009 From: subscr1024 at mail.ru (Subscriber) Date: Sun Jan 25 12:49:43 2009 Subject: WINE in jail [Was: i386_set_ldt and wine on AMD64] In-Reply-To: <20090124132823.GA6834@deviant.kiev.zoral.com.ua> References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com> <20061231003901.GA76688@slackbox.xs4all.nl> <20081212130631.GC2038@deviant.kiev.zoral.com.ua> <49427649.20006@lapo.it> <20081212145015.GE2038@deviant.kiev.zoral.com.ua> <4979D9F5.6020105@mail.ru> <20090124132823.GA6834@deviant.kiev.zoral.com.ua> Message-ID: <497CCF58.4000204@mail.ru> Hello, Kostik. Kostik Belousov ?????: > What is "8C" system ? Eight-core ? No, 8-CURRENT. :) My system is Turion TL-64 based notebook, 2 cores, 4G of RAM. > First, what was the version of the patch ? All publically released > patches are no longer applicable to the HEAD. The latest version is > at > http://people.freebsd.org/~kib/misc/amd64_ctx.3.patch Thanks. Now I start compilation of new kernel, will test it right now. > Did you tried to run wine/i386 on the box ? No. My notebook used for working, and unstable xorg is critical issue for me. Thus I rolled back to old kernel and wrote question to this list. > To debug the issue with Xorg, I need to look at the instruction where > the code faults. Specifically, please enable coredump from Xorg, load > coredump in gdb (like gdb Xorg Xorg.core) and then > info registers > > disassemble <%rip value> <%rip value>+0x10 Ok. I'll do it, if xorg will crashed again. But now new xorg 7.4 came to the ports, so I'll delay my answer for 2 or 3 days. > Thanks for testing. It is in my favor too. :) From bugmaster at FreeBSD.org Mon Jan 26 03:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 26 04:12:04 2009 Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org Message-ID: <200901261106.n0QB6qDG024188@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 -------------------------------------------------------------------------------- f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 o amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute 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/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127787 amd64 [lor] 3 lock LOR in recent CURRENT o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- 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 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/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 90 problems total. From oliver.pntr at gmail.com Tue Jan 27 06:05:32 2009 From: oliver.pntr at gmail.com (Oliver Pinter) Date: Tue Jan 27 06:05:44 2009 Subject: Problems with ata driver on current / Asus P5Q-E In-Reply-To: <00163641792bd5eece046142843d@google.com> References: <6101e8c40901240749h106916adya7d6a8caee4ed155@mail.gmail.com> <00163641792bd5eece046142843d@google.com> Message-ID: <6101e8c40901270605g68d3bc3esc89c65841c82fbcd@mail.gmail.com> add S?ren to CC On 1/25/09, scott.gasch@gmail.com wrote: > Hi Oliver, > > Thanks for the reply. I'm running bios version 02.61 American Megatrends > Inc; it has never been updated. I just got the latest image (1703) from > ASUS and will try flashing it. > > I don't have my controller set on RAID because I don't want hardware > RAID... it's set on AHCI instead. Maybe this is the difference. Are you > doing hardware RAID? > > I'm still looking over your config and dmesg, thanks for sending those. > I'll report back if I figure anything out. > > Thx, > Scott > > > On Jan 24, 2009 7:49am, Oliver Pinter wrote: >> I have the same MB, and it running perfect, but I have only 3 SATA HDD >> >> + 1 SATA DVD-RW >> >> >> >> The ICH is in RAID mode. >> >> >> >> Attached my conf and dmesg >> >> >> >> Which version of BIOS use You? >> >> >> >> [snip] >> >> Southbridge >> >> - 6 x SATA 3Gb/s >> >> - Intel(R) Matrix Storage Technology with RAID 0, 1, 5, 10 support >> >> Marvell 88SE6121 >> >> - 1 x UltraDMA 133/100/66 for up to 2 PATA devices >> >> - 1 x External SATA 3Gb/s port (SATA On-the-Go) >> >> Silicon Image Sil5723 (Drive Xpert technology) >> >> - 2 x SATA 3Gb/s >> >> - Supports EZ Backup and Super Speed functions >> >> [snip] >> >> >> >> > http://www.asus.com/products.aspx?l1=3&l2=11&l3=709&l4=0&model=2267&modelmenu=2 >> >> >> >> /* sorry for bad english */ >> >> >> >> On 1/24/09, Scott Gasch scott.gasch@gmail.com> wrote: >> >> > Hi, >> >> > I've been running a 7.1-p1 (amd64) system and and seeing very high > interrupt >> >> > rates on irq19 which is shared between several devices. Over 60% of one >> >> > core is used responding to interrupts. The machine also hangs > frequently. >> >> > irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... >> >> > the consensus response to my last question was that "it's probably the > ata >> >> > driver". >> >> > >> >> > Today I tried building and booting a GENERIC current kernel and got > another >> >> > piece of information. The freebsd-current GENERIC kernel does not boot; >> >> > shortly after probing the drives it says "Cannot setup DMA" several > times on >> >> > the console and hangs. >> >> > >> >> > This machine is an Asus P5Q-E... I believe it has two ATA controllers: >> >> > a Marvell >> >> > 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets > generating >> >> > interrupts that the driver doesn't understand and/or properly dismiss? > Can >> >> > it be put into a legacy mode that works? This machine has problems in > 7.0, >> >> > 7.1 and current... I'm running out of ideas. >> >> > >> >> > Thx, >> >> > Scott >> >> > _______________________________________________ >> >> > freebsd-current@freebsd.org mailing list >> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> >> > To unsubscribe, send any mail > to "freebsd-current-unsubscribe@freebsd.org" >> >> > >> > From oliver.pntr at gmail.com Tue Jan 27 14:37:22 2009 From: oliver.pntr at gmail.com (Oliver Pinter) Date: Tue Jan 27 14:39:48 2009 Subject: Problems with ata driver on current / Asus P5Q-E In-Reply-To: <00163641792bd5eece046142843d@google.com> References: <6101e8c40901240749h106916adya7d6a8caee4ed155@mail.gmail.com> <00163641792bd5eece046142843d@google.com> Message-ID: <6101e8c40901270605g68d3bc3esc89c65841c82fbcd@mail.gmail.com> add S?ren to CC On 1/25/09, scott.gasch@gmail.com wrote: > Hi Oliver, > > Thanks for the reply. I'm running bios version 02.61 American Megatrends > Inc; it has never been updated. I just got the latest image (1703) from > ASUS and will try flashing it. > > I don't have my controller set on RAID because I don't want hardware > RAID... it's set on AHCI instead. Maybe this is the difference. Are you > doing hardware RAID? > > I'm still looking over your config and dmesg, thanks for sending those. > I'll report back if I figure anything out. > > Thx, > Scott > > > On Jan 24, 2009 7:49am, Oliver Pinter wrote: >> I have the same MB, and it running perfect, but I have only 3 SATA HDD >> >> + 1 SATA DVD-RW >> >> >> >> The ICH is in RAID mode. >> >> >> >> Attached my conf and dmesg >> >> >> >> Which version of BIOS use You? >> >> >> >> [snip] >> >> Southbridge >> >> - 6 x SATA 3Gb/s >> >> - Intel(R) Matrix Storage Technology with RAID 0, 1, 5, 10 support >> >> Marvell 88SE6121 >> >> - 1 x UltraDMA 133/100/66 for up to 2 PATA devices >> >> - 1 x External SATA 3Gb/s port (SATA On-the-Go) >> >> Silicon Image Sil5723 (Drive Xpert technology) >> >> - 2 x SATA 3Gb/s >> >> - Supports EZ Backup and Super Speed functions >> >> [snip] >> >> >> >> > http://www.asus.com/products.aspx?l1=3&l2=11&l3=709&l4=0&model=2267&modelmenu=2 >> >> >> >> /* sorry for bad english */ >> >> >> >> On 1/24/09, Scott Gasch scott.gasch@gmail.com> wrote: >> >> > Hi, >> >> > I've been running a 7.1-p1 (amd64) system and and seeing very high > interrupt >> >> > rates on irq19 which is shared between several devices. Over 60% of one >> >> > core is used responding to interrupts. The machine also hangs > frequently. >> >> > irq19 is shared by atapci1, atapci2, fwohci0 and uhci4... >> >> > the consensus response to my last question was that "it's probably the > ata >> >> > driver". >> >> > >> >> > Today I tried building and booting a GENERIC current kernel and got > another >> >> > piece of information. The freebsd-current GENERIC kernel does not boot; >> >> > shortly after probing the drives it says "Cannot setup DMA" several > times on >> >> > the console and hangs. >> >> > >> >> > This machine is an Asus P5Q-E... I believe it has two ATA controllers: >> >> > a Marvell >> >> > 88SE6121 and a Silicon Image SIL5723. Is one of these chipsets > generating >> >> > interrupts that the driver doesn't understand and/or properly dismiss? > Can >> >> > it be put into a legacy mode that works? This machine has problems in > 7.0, >> >> > 7.1 and current... I'm running out of ideas. >> >> > >> >> > Thx, >> >> > Scott >> >> > _______________________________________________ >> >> > freebsd-current@freebsd.org mailing list >> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> >> > To unsubscribe, send any mail > to "freebsd-current-unsubscribe@freebsd.org" >> >> > >> > _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From roar.pettersen at it.uib.no Sat Jan 31 07:30:03 2009 From: roar.pettersen at it.uib.no (Roar Pettersen) Date: Sat Jan 31 08:09:47 2009 Subject: amd64/131209: 7.1-STABLE amd64 crash Message-ID: <200901311529.n0VFTj73014198@www.freebsd.org> >Number: 131209 >Category: amd64 >Synopsis: 7.1-STABLE amd64 crash >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 31 15:30:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Roar Pettersen >Release: FreeBSD 7.1-STABLE >Organization: University of Bergen >Environment: FreeBSD proxy-gw2.uib.no 7.1-STABLE FreeBSD 7.1-STABLE #0: Fri Jan 30 16:59:50 CET 2009 root@proxy-gw2.uib.no:/usr/obj/usr/src/sys/PROXY-GW2 amd64 >Description: After 6 hours the system crash / freeze : # kgdb kernel.debug /var/crash/vmcore.0 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 = 1; apic id = 01 fault virtual address = 0x800000108 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff8037690c stack pointer = 0x10:0xfffffffec329e5e0 frame pointer = 0x10:0x0 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 = 25972 (cron) trap number = 12 panic: page fault cpuid = 1 Uptime: 6h33m10s Physical memory: 2039 MB Dumping 411 MB: 396 380 364 348 332 316 300 284 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12 Reading symbols from /boot/kernel/blank_saver.ko...Reading symbols from /boot/kernel/blank_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/blank_saver.ko #0 0xffffffff802fa8fa in doadump () at /usr/src/sys/kern/kern_shutdown.c:238 238 if (dumper.dumper == NULL) { Powe on / Off was the solution to re-start the system. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: