Re[2]: 2 day GENERIC-current eat 2 CPU core at 100%
Great thanx ! It working ! :) Thu, 09 Jun 2011 19:40:18 +0300 письмо от Alexander Motin m...@freebsd.org: Andrey Smagin wrote: Hi, yesterday I tried switch event timer on i8254 - it do nothing. I disabled hyperthreading - now eat from 50% to 100% All dmesg is lines: (noperiph:ata3:0:-1:-1): rescan already queued (noperiph:ata3:0:-1:-1): rescan already queued (noperiph:ata2:0:-1:-1): rescan already queued (noperiph:ata3:0:-1:-1): rescan already queued (noperiph:ata3:0:-1:-1): rescan already queued I boot FreeBSD from USB with no ATA - may be it is. These messages are not what I expected to see, but they tell me that your problem may be SATA related. I've got the same Intel D525MW board and think reproduced the problem. I hope I've even fixed it. :) Retry please with fresh CURRENT sources or at least with this patch applied: http://svn.freebsd.org/changeset/base/222897 Wed, 08 Jun 2011 20:34:42 +0300 письмо от Alexander Motin m...@freebsd.org: On 07.06.2011 20:12, Andrey Smagin wrote: vmstat -i interrupt total rate irq16: uhci3 205 0 irq20: hpet0 147924380 1126 irq23: uhci0 ehci0 522517 3 total148447102 1130 Tue, 7 Jun 2011 10:34:01 +0200 письмо от Hans Petter Selaskyhsela...@c2i.net: On Tuesday 07 June 2011 10:09:47 Andrey Smagin wrote: I upgraded 2 day ago from 2010-current box on Intel D525MW. System very slow down after that. kern.hz=50 in systat -vmstat - 140hpet interrupts/s at top 25% in interrupts 25% in system because hyperthreading system found 4 cpu. What does vmstat -i output? Send me please full verbose dmesg and output of the `sysctl kern.eventtimer` and `sysctl kern.timecounter`. Try to switch to another timer: sysctl kern.eventtimer.timer=LAPIC Try to switch to periodic timers (instead): sysctl kern.eventtimer.periodic=1 -- Alexander Motin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior
On 10.06.2011 10:50, Eir Nym wrote: messages on the start of this dmesg are for more pages of (I have see them for several seconds on same hardware) kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF You have mixed old partitioning classes with GEOM_PART. You should remove from the kernel at least: options GEOM_BSD options GEOM_MBR options GEOM_PC98 options GEOM_VOL -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior
2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru: On 10.06.2011 10:50, Eir Nym wrote: messages on the start of this dmesg are for more pages of (I have see them for several seconds on same hardware) kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF You have mixed old partitioning classes with GEOM_PART. You should remove from the kernel at least: options GEOM_BSD options GEOM_MBR options GEOM_PC98 options GEOM_VOL This should be documented. -- WBR, Andrey V. Elsukov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD extended to Arab World
Hello, 2011/6/10 Mohammed Farrag mfar...@freebsd.org: Hi, Thanks for your reply. On Fri, Jun 10, 2011 at 1:08 AM, Philip Paeps phi...@freebsd.org wrote: On 9 Jun 2011, at 22:15, Mohammed Farrag wrote: First I introduce myself, Mohammed Farrag, ArabBSD Project Manager and FreeBSD Contributor. We have a project to extend FreeBSD in Arab world. Nice initiative! Our website is https://sites.google.com/site/arabbsd/ and our facebook group is http://www.facebook.com/home.php?sk=group_114438501975285ap=1 I will be glad to receive your comments/ and recommendations. I don't think the Start FreeBSD page on the website should be linking to an unofficial source for VMWare... Pointing to http://vmware.com/ may be more suitable. Sorry for that. I will redirect it. VMware.Workstation.v7.1.261024.Incl.Keymaker-EMBRACE.part1.rar The FreeBSD project probably does not want to be associated with unauthorized distribution of proprietary software. Maybe you could suggest running FreeBSD in VirtualBox : http://www.virtualbox.org/ It's free, open source, and better supported by FreeBSD. You can run FreeBSD as a VirtualBox guest : http://www.freshports.org/emulators/virtualbox-ose-additions/ And run VirtualBox in a FreeBSD host : http://www.freshports.org/emulators/virtualbox-ose/ Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD extended to Arab World
Hi, On Fri, Jun 10, 2011 at 8:25 AM, C. P. Ghost cpgh...@cordula.ws wrote: On Thu, Jun 9, 2011 at 10:15 PM, Mohammed Farrag mfar...@freebsd.org wrote: Hi Community, First I introduce myself, Mohammed Farrag, ArabBSD Project Manager and FreeBSD Contributor. We have a project to extend FreeBSD in Arab world. We aim to work in two direction. First, we will translate FreeBSD Documentation and learning tutorials to Arabic. Second, we will have summer training for starting work on FreeBSD development. Our website is https://sites.google.com/site/arabbsd/ and our facebook group is http://www.facebook.com/home.php?sk=group_114438501975285ap=1 I will be glad to receive your comments/ and recommendations. Great idea! Maybe we can hope to see more stuff from arabeyes in /usr/ports/arabic as well? http://projects.arabeyes.org/index.php We have our plans to develop Arab Tutorials, documentation and ports. Sure, arabeyes will be one of our plans. Of course, you could also announce ArabBSD there... ;-) Regards, -- *Mohammed Farrag* -cpghost. -- Cordula's Web. http://www.cordula.ws/ -- *Mohammed Farrag* *FreeBSD Contributor* ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD extended to Arab World
On Fri, Jun 10, 2011 at 10:37 AM, Olivier Smedts oliv...@gid0.org wrote: Hello, 2011/6/10 Mohammed Farrag mfar...@freebsd.org: Hi, Thanks for your reply. On Fri, Jun 10, 2011 at 1:08 AM, Philip Paeps phi...@freebsd.org wrote: On 9 Jun 2011, at 22:15, Mohammed Farrag wrote: First I introduce myself, Mohammed Farrag, ArabBSD Project Manager and FreeBSD Contributor. We have a project to extend FreeBSD in Arab world. Nice initiative! Our website is https://sites.google.com/site/arabbsd/ and our facebook group is http://www.facebook.com/home.php?sk=group_114438501975285ap=1 I will be glad to receive your comments/ and recommendations. I don't think the Start FreeBSD page on the website should be linking to an unofficial source for VMWare... Pointing to http://vmware.com/ may be more suitable. Sorry for that. I will redirect it. VMware.Workstation.v7.1.261024.Incl.Keymaker-EMBRACE.part1.rar The FreeBSD project probably does not want to be associated with unauthorized distribution of proprietary software. Maybe you could suggest running FreeBSD in VirtualBox : http://www.virtualbox.org/ It's free, open source, and better supported by FreeBSD. You can run FreeBSD as a VirtualBox guest : http://www.freshports.org/emulators/virtualbox-ose-additions/ And run VirtualBox in a FreeBSD host : http://www.freshports.org/emulators/virtualbox-ose/ VirtualBox is Free but has some problems with running some releases of FreeBSD. Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email vCards X www: http://www.gid0.org- against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. -- *Mohammed Farrag* *FreeBSD Contributor* ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pcib allocation failure
On Thursday, June 09, 2011 6:08:08 pm deeptec...@gmail.com wrote: On Thu, Jun 9, 2011 at 8:56 PM, John Baldwin j...@freebsd.org wrote: On Thursday, June 09, 2011 2:07:31 pm deeptec...@gmail.com wrote: pcib1: attempting to grow prefetch window for (0xe000-0xefff,0x1000) back candidate range: 0xe000-0xefff pcib1: failed to grow prefetch window to 0xd000-0xefff: 6 Hmm, ENXIO is an odd error. rman_adjust_resource() can't fail with that. Oh, I missed adding bus_adjust_resource() to the x86 nexus drivers. :( alright, with that patch the machine is back in business. Great! Thanks for testing. I'll commit these fixes today. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
udav: vendor 0x0fe6, product: 0x9700
Hi list,
I'm trying to add a new product id [1] to the driver udav and am
having a little trouble.
At first, this is similar to id 0x8180 and there should be no
problems, but I still can not get a PHY for it.
Can someone help me?
System:
freekazoide# uname -a
FreeBSD freekazoide.luizgustavo.pro.br 9.0-CURRENT FreeBSD 9.0-CURRENT
#5 r222586M: Thu Jun 2 12:11:33 BRT 2011
r...@freekazoide.luizgustavo.pro.br:/usr/obj/usr/src/sys/GENERIC i386
Dmesg:
ugen0.2: vendor 0x0fe6 at usbus0
udav0: vendor 0x0fe6 USB 2.0 10100M Ethernet Adaptor, class 0/0, rev
1.10/1.01, addr 2 on usbus0
udav0: attaching PHYs failed
About adapter:
[1] http://www.luizgustavo.pro.br/~lgcosta/jp1080/
Patch:
diff -r 4dc08fdbcf2f sys/dev/usb/net/if_udav.c
--- a/sys/dev/usb/net/if_udav.c Thu Jun 09 18:32:21 2011 -0300
+++ b/sys/dev/usb/net/if_udav.c Thu Jun 09 18:30:38 2011 -0300
@@ -210,6 +210,7 @@
{USB_VPI(USB_VENDOR_SHANTOU, USB_PRODUCT_SHANTOU_ADM8515, 0)},
/* Kontron AG USB Ethernet */
{USB_VPI(USB_VENDOR_KONTRON, USB_PRODUCT_KONTRON_DM9601, 0)},
+ {USB_VPI(USB_VENDOR_KONTRON, USB_PRODUCT_KONTRON_JP1082, 0)},
};
static void
diff -r 4dc08fdbcf2f sys/dev/usb/usbdevs
--- a/sys/dev/usb/usbdevs Thu Jun 09 18:32:21 2011 -0300
+++ b/sys/dev/usb/usbdevs Thu Jun 09 18:30:38 2011 -0300
@@ -2014,6 +2014,7 @@
/* Kontron AG products */
product KONTRON DM9601 0x8101 USB Ethernet
+product KONTRON JP1082 0x9700 USB Ethernet
/* Konica Corp. Products */
product KONICA CAMERA 0x0720 Digital Color Camera
--
/\ Luiz Gustavo S. Costa
/ \ Programmer at BSD Perimeter
/ \ /\/\/\ Visit the pfSense Project
/ \ \ \ http://www.pfsense.org
-
BSD da serra carioca, Teresopolis (visite: http://miud.in/Inv)
Contatos: luizgust...@luizgustavo.pro.br / lgco...@pfsense.org
Blog: http://www.luizgustavo.pro.br
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff
On Wednesday, June 08, 2011 6:30:37 pm John wrote: - John Baldwin's Original Message - On Wednesday, June 08, 2011 12:13:05 am John wrote: - John Baldwin's Original Message - On Monday, June 06, 2011 9:33:30 pm John wrote: - John Baldwin's Original Message - On Sunday, June 05, 2011 8:23:53 pm John wrote: I just attempted to update an HP385G0 system from current as of 4-15-2011 to 6-2-2011. The new system will not boot, and shows the following message when it hangs: I applied your patch/rebuilt/installed/rebooted. The system seems to get farther, but still locks up tight. A screen pic is here: http://people.freebsd.org/~jwd/dmesg.jpg Hmmm, an MCA is not a good sign. Yes, there are multiple ranges. Would it be possible to use a serial port to capture a full verbose dmesg up to the point where it hangs? -- John Baldwin Hi John Yes, I did get a serial console ilo configured on the system today. I've attached two verbose consoles. The 1st is from -current as of today which fails to boot. The 2nd is from earlier this year which boot correctly. Humm, is the first with any patches applied? Earlier you reported a problem that occured much later (failing to allocate the initial window) but in your new dmesg it isn't getting that far. Sorry John, here's the verbose dmesg output with your patch applied. This is at the tail of the console: pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of pci0:1:3:0 map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[18]: type Memory, range 32, base 0xf5ff, size 12, enabled Output ends with a single 'M', not MCA as earlier. Can you revert any patches I've sent you and update to the latest HEAD (I just committed some bugfixes) and try it out please? -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff
on 09/06/2011 15:57 John Baldwin said the following: On Thursday, June 09, 2011 2:11:16 am Andriy Gapon wrote: on 09/06/2011 01:30 John said the following: Sorry John, here's the verbose dmesg output with your patch applied. This is at the tail of the console: pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of pci0:1:3:0 map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[18]: type Memory, range 32, base 0xf5ff, size 12, enabled Output ends with a single 'M', not MCA as earlier. Just a wild guess - what happens if you revert r222537 (you might need to revert r222804 first)? I think he's getting a MCA due to writing to a bad address and getting a PCI-e target abort equivalent and that the screen output is broken because the VGA device is what is probably getting hosed by the pcib driver. Given that, I doubt the printf changes are related. Right. I was mostly curious if printf has become broken with respect to things like reporting MCEs. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gcc-4.5 and 4.6 needs to be recompiled due to /usr/src/UPDATE: 20110608:
On Thu, Jun 9, 2011 at 3:26 PM, Attilio Rao atti...@freebsd.org wrote: 2011/6/9 Michael Butler i...@protected-networks.net: On 06/09/11 17:18, Attilio Rao wrote: 2011/6/9 Mark Linimon lini...@lonesome.com: Things that change the way the base system behaves w/rt ports need version bumps. BTW, could someone provide an actual error message? I assume these errors are caused by cpumask_t going away. For emulators/virtualbox-ose-kmod .. cc -O2 -pipe -march=prescott -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c: In function 'RTMpOnOthers': /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: 'cpumask_t' undeclared (first use in this function) /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: (Each undeclared identifier is reported only once /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: for each function it appears in.) Without a version bump, it becomes impossible to determine if a version-specific patch can be applied to accommodate the ABI change, Well, the ports should be working against -CURRENT, so what you say is not entirely true. Second thing, yeah, it is cpumask_t going away, so someone needs to sit there, check what usage of cpumask_t was done and replace with proper code. It seems usual port maintenance due by the maintainer IMHO. I'm not entirely sure how bumping __FreeBSD_version may help right now. This also impacts recompiling the base system if you don't nuke /usr/obj (output from make buildworld buildkernel, no -j). Thanks, -Garrett c++ -O2 -pipe -fno-strict-aliasing -pipe -I/usr/obj/usr/src/sys/FALLOUT -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/list-node.cc c++ -O2 -pipe -fno-strict-aliasing -pipe -I/usr/obj/usr/src/sys/FALLOUT -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc In file included from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc:25: /usr/include/sys/types.h:102: error: '__cpumask_t' does not name a type *** Error code 1 Stop in /usr/src/gnu/usr.bin/gperf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gcc-4.5 and 4.6 needs to be recompiled due to /usr/src/UPDATE: 20110608:
On Fri, Jun 10, 2011 at 8:22 AM, Garrett Cooper yaneg...@gmail.com wrote: On Thu, Jun 9, 2011 at 3:26 PM, Attilio Rao atti...@freebsd.org wrote: 2011/6/9 Michael Butler i...@protected-networks.net: On 06/09/11 17:18, Attilio Rao wrote: 2011/6/9 Mark Linimon lini...@lonesome.com: Things that change the way the base system behaves w/rt ports need version bumps. BTW, could someone provide an actual error message? I assume these errors are caused by cpumask_t going away. For emulators/virtualbox-ose-kmod .. cc -O2 -pipe -march=prescott -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c: In function 'RTMpOnOthers': /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: 'cpumask_t' undeclared (first use in this function) /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: (Each undeclared identifier is reported only once /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/mp-r0drv-freebsd.c:167: error: for each function it appears in.) Without a version bump, it becomes impossible to determine if a version-specific patch can be applied to accommodate the ABI change, Well, the ports should be working against -CURRENT, so what you say is not entirely true. Second thing, yeah, it is cpumask_t going away, so someone needs to sit there, check what usage of cpumask_t was done and replace with proper code. It seems usual port maintenance due by the maintainer IMHO. I'm not entirely sure how bumping __FreeBSD_version may help right now. This also impacts recompiling the base system if you don't nuke /usr/obj (output from make buildworld buildkernel, no -j). Thanks, -Garrett c++ -O2 -pipe -fno-strict-aliasing -pipe -I/usr/obj/usr/src/sys/FALLOUT -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/list-node.cc c++ -O2 -pipe -fno-strict-aliasing -pipe -I/usr/obj/usr/src/sys/FALLOUT -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-strict-aliasing -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc In file included from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc:25: /usr/include/sys/types.h:102: error: '__cpumask_t' does not name a type *** Error code 1 Stop in /usr/src/gnu/usr.bin/gperf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I just realized that my environment may be at fault for this item (I was trying to debug something -- note the first -I argument). Please ignore and move on unless more reports come in. Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff
- John Baldwin's Original Message - On Thursday, June 09, 2011 2:11:16 am Andriy Gapon wrote: on 09/06/2011 01:30 John said the following: Sorry John, here's the verbose dmesg output with your patch applied. This is at the tail of the console: pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of pci0:1:3:0 map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[18]: type Memory, range 32, base 0xf5ff, size 12, enabled Output ends with a single 'M', not MCA as earlier. Just a wild guess - what happens if you revert r222537 (you might need to revert r222804 first)? I think he's getting a MCA due to writing to a bad address and getting a PCI-e target abort equivalent and that the screen output is broken because the VGA device is what is probably getting hosed by the pcib driver. Given that, I doubt the printf changes are related. Just for grins, I decided to completely remove usb from the kernel to see if it might help. Nolonger prints the MCA and/or M, just hangs while printing out the no driver attached messages. Still prints out the failed to allocate messages... found- vendor=0x0e11, dev=0xb203, revid=0x01 domain=0, bus=1, slot=2, func=0 class=08-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0103, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x4800, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[14]: type Memory, range 32, base 0xf7cb, size 9, enabled pcib1: allocated memory range (0xf7cb-0xf7cb01ff) for rid 14 of pci0:1:2:0 pcib1: matched entry for 1.2.INTA pcib1: slot 2 INTA hardwired to IRQ 16 found- vendor=0x0e11, dev=0xb204, revid=0x01 domain=0, bus=1, slot=2, func=2 class=08-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0197, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x4000, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[14]: type Memory, range 32, base 0xf7ca, size 11, enabled pcib1: allocated memory range (0xf7ca-0xf7ca07ff) for rid 14 of pci0:1:2:2 map[18]: type Memory, range 32, base 0xf7c9, size 13, enabled pcib1: allocated memory range (0xf7c9-0xf7c91fff) for rid 18 of pci0:1:2:2 map[1c]: type Memory, range 32, base 0xf7c0, size 19, enabled pcib1: allocated memory range (0xf7c0-0xf7c7) for rid 1c of pci0:1:2:2 pcib1: matched entry for 1.2.INTB pcib1: slot 2 INTB hardwired to IRQ 17 found- vendor=0x1002, dev=0x4752, revid=0x27 domain=0, bus=1, slot=3, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xf600, size 24, enabled pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of pci0:1:3:0 map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) map[18]: type Memory, range 32, base 0xf5ff, size 12, enabled pcib1: allocated memory range (0xf5ff-0xf5ff0fff) for rid 18 of pci0:1:3:0 pci1: serial bus, USB at device 0.0 (no driver attached) pci1: serial bus, USB at device 0.1 (no driver attached) pci1: base peripheral at device 2.0 (no driver attached) pci1: base peripheral at device 2.2 ^ no output after this. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
9.0-CURRENT-201105-amd64 install kernel panic
Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick the kernel panics: panic: m_getzone: m_getjcl: invalid cluster type http://www.flickr.com/photos/opensolaris/5818432532/in/photostream The hardware is: http://www.supermicro.com/products/motherboard/QPI/5500/X8DTL-3F.cfm The cpu's are Intel 5520 and the nics are 82574L FWIW this appears to be similar to a recently reported panic with 8-STABLE: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062596.html Any help is very greatly apprecated. thanks -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: udav: vendor 0x0fe6, product: 0x9700
On 10 June 2011 14:17, Luiz Gustavo S. Costa lgco...@pfsense.org wrote: I'm trying to add a new product id [1] to the driver udav and am having a little trouble. At first, this is similar to id 0x8180 and there should be no problems, but I still can not get a PHY for it. Assuming you mean 0x8181 --looking at your patch-- How do you know they have similar chip-sets? Can you get the full interface description list for both to see if they have the same endpoints: usbconfig dump_all_config_desc Can someone help me? ... About adapter: [1] http://www.luizgustavo.pro.br/~lgcosta/jp1080/ Looking at the picture these kind of USB dongles (various chipsets) tend to die. I suspect the build quality is not that great. Just checking you did check it the device is functioning properly using the official (linux) drivers? Br. /Rick -- http://rickvanderzwet.nl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff
On Friday, June 10, 2011 11:00:15 am John wrote:
- John Baldwin's Original Message -
On Thursday, June 09, 2011 2:11:16 am Andriy Gapon wrote:
on 09/06/2011 01:30 John said the following:
Sorry John, here's the verbose dmesg output with your patch applied.
This is at the tail of the console:
pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of
pci0:1:3:0
map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled
pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000)
map[18]: type Memory, range 32, base 0xf5ff, size 12,
enabled
Output ends with a single 'M', not MCA as earlier.
Just a wild guess - what happens if you revert r222537 (you might need to
revert
r222804 first)?
I think he's getting a MCA due to writing to a bad address and getting a
PCI-e target abort equivalent and that the screen output is broken
because the VGA device is what is probably getting hosed by the pcib driver.
Given that, I doubt the printf changes are related.
Just for grins, I decided to completely remove usb from the kernel
to see if it might help. Nolonger prints the MCA and/or M, just
hangs while printing out the no driver attached messages. Still
prints out the failed to allocate messages...
Hmmm. Your case is a bit different. PCI-PCI bridges have to allocate I/O
space on 4KB boundarys, so the smallest chunk it can allocate for the
resources behind your bridge is 0x4000-0x4fff which is what keeps failing.
Hmm, it's claiming that brgphy1 has some I/O ports that conflict allocated.
That makes no sense. brgphy devices have no I/O port resources. I think
the device_t got reused.
Can you try this perhaps to get started relative to sys/x86/x86/nexus.c:
Index: nexus.c
===
--- nexus.c (revision 222932)
+++ nexus.c (working copy)
@@ -388,6 +388,27 @@ nexus_alloc_resource(device_t bus, device_t child,
if (rm == NULL)
return (NULL);
+ /* XXX: Hack */
+ if (type == SYS_RES_IOPORT start = 0x4000 start = 0x4) {
+ char *buf;
+
+ device_printf(bus, allocating range %#lx-%#lx for child,
+ start, end);
+ if (device_get_nameunit(child) != NULL)
+ printf( %s, device_get_nameunit(child));
+ printf( of %s\n, device_get_nameunit(
+ device_get_parent(child)));
+ buf = malloc(1024, M_DEVBUF, M_WAITOK);
+ *buf = '\0';
+ bus_child_pnpinfo_str(dev, buf, 1024);
+ if (*buf != '\0')
+ printf(\t%s\n, buf);
+ *buf = '\0';
+ bus_child_location_str(dev, buf, 1024);
+ if (*buf != '\0')
+ printf(\tat %s\n, buf);
+ free(buf, M_DEVBUF);
+ }
rv = rman_reserve_resource(rm, start, end, count, flags, child);
if (rv == 0)
return 0;
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: udav: vendor 0x0fe6, product: 0x9700
Hi Rick, 2011/6/10 Rick van der Zwet i...@rickvanderzwet.nl: On 10 June 2011 14:17, Luiz Gustavo S. Costa lgco...@pfsense.org wrote: I'm trying to add a new product id [1] to the driver udav and am having a little trouble. At first, this is similar to id 0x8180 and there should be no problems, but I still can not get a PHY for it. Assuming you mean 0x8181 --looking at your patch-- How do you know they have similar chip-sets? Can you get the full interface description list for both to see if they have the same endpoints: usbconfig dump_all_config_desc Yes... I will find here the link that describes this: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commit;h=67158cebde60edb1a11cf4743f1cb9ded847c5fc Can someone help me? ... About adapter: [1] http://www.luizgustavo.pro.br/~lgcosta/jp1080/ Looking at the picture these kind of USB dongles (various chipsets) tend to die. I suspect the build quality is not that great. Just checking you did check it the device is functioning properly using the official (linux) drivers? Yes, it's a very cheap adapter, can be found on ebay easily. And yes, he normally works in linux, I am posting a link to the code and it is observed, the only difference are exactly the entries id of the product. http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=blob;f=drivers/net/usb/dm9601.c;h=5002f5be47be7dcbd95e0fd9cee2a80910046a81;hb=HEAD Br. /Rick -- http://rickvanderzwet.nl Thanks -- /\ Luiz Gustavo S. Costa / \ Programmer at BSD Perimeter / \ /\/\/\ Visit the pfSense Project / \ \ \ http://www.pfsense.org - BSD da serra carioca, Teresopolis (visite: http://miud.in/Inv) Contatos: luizgust...@luizgustavo.pro.br / lgco...@pfsense.org Blog: http://www.luizgustavo.pro.br ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: udav: vendor 0x0fe6, product: 0x9700
usbconfig dump_all_config_desc: http://www.luizgustavo.pro.br/~lgcosta/jp1080/usbconfig_all_desc.txt 2011/6/10 Luiz Gustavo S. Costa lgco...@pfsense.org: Hi Rick, 2011/6/10 Rick van der Zwet i...@rickvanderzwet.nl: On 10 June 2011 14:17, Luiz Gustavo S. Costa lgco...@pfsense.org wrote: I'm trying to add a new product id [1] to the driver udav and am having a little trouble. At first, this is similar to id 0x8180 and there should be no problems, but I still can not get a PHY for it. Assuming you mean 0x8181 --looking at your patch-- How do you know they have similar chip-sets? Can you get the full interface description list for both to see if they have the same endpoints: usbconfig dump_all_config_desc Yes... I will find here the link that describes this: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commit;h=67158cebde60edb1a11cf4743f1cb9ded847c5fc Can someone help me? ... About adapter: [1] http://www.luizgustavo.pro.br/~lgcosta/jp1080/ Looking at the picture these kind of USB dongles (various chipsets) tend to die. I suspect the build quality is not that great. Just checking you did check it the device is functioning properly using the official (linux) drivers? Yes, it's a very cheap adapter, can be found on ebay easily. And yes, he normally works in linux, I am posting a link to the code and it is observed, the only difference are exactly the entries id of the product. http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=blob;f=drivers/net/usb/dm9601.c;h=5002f5be47be7dcbd95e0fd9cee2a80910046a81;hb=HEAD Br. /Rick -- http://rickvanderzwet.nl Thanks -- /\ Luiz Gustavo S. Costa / \ Programmer at BSD Perimeter / \ /\/\/\ Visit the pfSense Project / \ \ \ http://www.pfsense.org - BSD da serra carioca, Teresopolis (visite: http://miud.in/Inv) Contatos: luizgust...@luizgustavo.pro.br / lgco...@pfsense.org Blog: http://www.luizgustavo.pro.br -- /\ Luiz Gustavo S. Costa / \ Programmer at BSD Perimeter / \ /\/\/\ Visit the pfSense Project / \ \ \ http://www.pfsense.org - BSD da serra carioca, Teresopolis (visite: http://miud.in/Inv) Contatos: luizgust...@luizgustavo.pro.br / lgco...@pfsense.org Blog: http://www.luizgustavo.pro.br ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [PATCH] Simple tidy up of puc(4) bus driver
On Monday, May 23, 2011 10:39:02 am John Baldwin wrote:
This small patch makes the puc(4) bus drivers a little more friendly. It
should now list the port for each child device in the boot messages, and
devinfo -v should list the type and port of each child device in its output
as
well:
Can I get a volunteer to test these changes?
Index: puc_pci.c
===
--- puc_pci.c (revision 222126)
+++ puc_pci.c (working copy)
@@ -132,7 +132,9 @@
DEVMETHOD(bus_read_ivar, puc_bus_read_ivar),
DEVMETHOD(bus_setup_intr,puc_bus_setup_intr),
DEVMETHOD(bus_teardown_intr, puc_bus_teardown_intr),
-DEVMETHOD(bus_print_child, bus_generic_print_child),
+DEVMETHOD(bus_print_child, puc_bus_print_child),
+DEVMETHOD(bus_child_pnpinfo_str, puc_bus_child_pnpinfo_str),
+DEVMETHOD(bus_child_location_str,puc_bus_child_location_str),
DEVMETHOD(bus_driver_added, bus_generic_driver_added),
{ 0, 0 }
};
Index: puc_pccard.c
===
--- puc_pccard.c (revision 222126)
+++ puc_pccard.c (working copy)
@@ -82,7 +82,9 @@
DEVMETHOD(bus_read_ivar, puc_bus_read_ivar),
DEVMETHOD(bus_setup_intr,puc_bus_setup_intr),
DEVMETHOD(bus_teardown_intr, puc_bus_teardown_intr),
-DEVMETHOD(bus_print_child, bus_generic_print_child),
+DEVMETHOD(bus_print_child, puc_bus_print_child),
+DEVMETHOD(bus_child_pnpinfo_str, puc_bus_child_pnpinfo_str),
+DEVMETHOD(bus_child_location_str,puc_bus_child_location_str),
DEVMETHOD(bus_driver_added, bus_generic_driver_added),
{ 0, 0 }
};
Index: puc.c
===
--- puc.c (revision 222126)
+++ puc.c (working copy)
@@ -726,3 +726,41 @@
}
return (0);
}
+
+int
+puc_bus_print_child(device_t dev, device_t child)
+{
+ struct puc_port *port;
+ int retval;
+
+ port = device_get_ivars(child);
+ retval = 0;
+
+ retval += bus_print_child_header(dev, child);
+ retval += printf( at port %d, port-p_nr);
+ retval += bus_print_child_footer(dev, child);
+
+ return (retval);
+}
+
+int
+puc_bus_child_location_str(device_t dev, device_t child, char *buf,
+size_t buflen)
+{
+ struct puc_port *port;
+
+ port = device_get_ivars(child);
+ snprintf(buf, buflen, port=%d, port-p_nr);
+ return (0);
+}
+
+int
+puc_bus_child_pnpinfo_str(device_t dev, device_t child, char *buf,
+size_t buflen)
+{
+ struct puc_port *port;
+
+ port = device_get_ivars(child);
+ snprintf(buf, buflen, type=%d, port-p_type);
+ return (0);
+}
Index: puc_bfe.h
===
--- puc_bfe.h (revision 222126)
+++ puc_bfe.h (working copy)
@@ -82,9 +82,12 @@
int puc_bfe_detach(device_t);
int puc_bfe_probe(device_t, const struct puc_cfg *);
+int puc_bus_child_location_str(device_t, device_t, char *, size_t);
+int puc_bus_child_pnpinfo_str(device_t, device_t, char *, size_t);
struct resource *puc_bus_alloc_resource(device_t, device_t, int, int *,
u_long,
u_long, u_long, u_int);
int puc_bus_get_resource(device_t, device_t, int, int, u_long *, u_long *);
+int puc_bus_print_child(device_t, device_t);
int puc_bus_read_ivar(device_t, device_t, int, uintptr_t *);
int puc_bus_release_resource(device_t, device_t, int, int, struct resource
*);
int puc_bus_setup_intr(device_t, device_t, struct resource *, int,
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-CURRENT-201105-amd64 install kernel panic
On Fri, June 10, 2011 11:22 am, Kim Culhan wrote: Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick the kernel panics: panic: m_getzone: m_getjcl: invalid cluster type Found a ps2 keyboard works in the debugger (not usb) and backtrace is here: http://www.flickr.com/photos/opensolaris/5819107302/in/photostream -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-CURRENT-201105-amd64 install kernel panic
This recent commit changed the way that the value for size being passed to m_getjcl is initialized. Not seeing any obvious bugs, and not having any additional context I would guess that that you're receiving an interrupt before adapter-rx_mbuf_sz is set. I trust jfv@ to look in to this shortly. http://svnweb.freebsd.org/base/head/sys/dev/e1000/if_em.c?r1=214362r2=214363; Thanks On Fri, Jun 10, 2011 at 9:19 PM, Kim Culhan w8hd...@gmail.com wrote: On Fri, June 10, 2011 11:22 am, Kim Culhan wrote: Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick the kernel panics: panic: m_getzone: m_getjcl: invalid cluster type Found a ps2 keyboard works in the debugger (not usb) and backtrace is here: http://www.flickr.com/photos/opensolaris/5819107302/in/photostream -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior
On 10 June 2011 11:08, Eir Nym eir...@gmail.com wrote: 2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru: On 10.06.2011 10:50, Eir Nym wrote: messages on the start of this dmesg are for more pages of (I have see them for several seconds on same hardware) kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF You have mixed old partitioning classes with GEOM_PART. You should remove from the kernel at least: options GEOM_BSD options GEOM_MBR options GEOM_PC98 options GEOM_VOL This should be documented. [r222913] After rebuilding and reinstalling world without these options, anything become OK as I see. Thanks for advice. -- WBR, Andrey V. Elsukov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-CURRENT-201105-amd64 install kernel panic
Interrupts are not enabled til after that is set, so I don't think this theory works, sorry. Jack On Fri, Jun 10, 2011 at 12:48 PM, K. Macy km...@freebsd.org wrote: This recent commit changed the way that the value for size being passed to m_getjcl is initialized. Not seeing any obvious bugs, and not having any additional context I would guess that that you're receiving an interrupt before adapter-rx_mbuf_sz is set. I trust jfv@ to look in to this shortly. http://svnweb.freebsd.org/base/head/sys/dev/e1000/if_em.c?r1=214362r2=214363; Thanks On Fri, Jun 10, 2011 at 9:19 PM, Kim Culhan w8hd...@gmail.com wrote: On Fri, June 10, 2011 11:22 am, Kim Culhan wrote: Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick the kernel panics: panic: m_getzone: m_getjcl: invalid cluster type Found a ps2 keyboard works in the debugger (not usb) and backtrace is here: http://www.flickr.com/photos/opensolaris/http://www.flickr.com/photos/opensolaris/5819107302/in/photostream 5819107302/in/photostream -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-CURRENT-201105-amd64 install kernel panic
On 10 June 2011 19:48, K. Macy km...@freebsd.org wrote: This recent commit changed the way that the value for size being passed to m_getjcl is initialized. Not seeing any obvious bugs, and not having any additional context I would guess that that you're receiving an interrupt before adapter-rx_mbuf_sz is set. I trust jfv@ to look in to this shortly. http://svnweb.freebsd.org/base/head/sys/dev/e1000/if_em.c?r1=214362r2=214363; Thanks You can try my custom kernel world if you find it applicable for your tasks. I use it for my computer http://eroese.org/_/_/pub/bsd/222913 I don't know how to roll world and kernel to USB image without mount and other privileges, so you need to tar -xpf world and kernel. On Fri, Jun 10, 2011 at 9:19 PM, Kim Culhan w8hd...@gmail.com wrote: On Fri, June 10, 2011 11:22 am, Kim Culhan wrote: Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick the kernel panics: panic: m_getzone: m_getjcl: invalid cluster type Found a ps2 keyboard works in the debugger (not usb) and backtrace is here: http://www.flickr.com/photos/opensolaris/5819107302/in/photostream -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: any place to look at for PCI-express performance issues ?
On Thu, Jun 09, 2011 at 09:11:51AM -0400, John Baldwin wrote: On Wednesday, June 08, 2011 11:59:52 pm Luigi Rizzo wrote: hi, during my tests with netmap with 10Gbit cards (82599, dual port), i notice that a motherboard with an AMD 880G chipset is performing significantly worse than an intel based one. In both cases the NIC is mounted on a 16x PCIe slot, and in both cases the driver reports the use 5Gb/4x per port. On the intel i reach easily 14.88Mpps, on the AMD the card tops at 1.8Mpps, and is not CPU limited (changing dev.cpu.0.freq does not change the throughput). Disabling flow control does not help (and in any case the other end of the link is the same), and since I am using the same picobsd image (based on FreeBSD/i386 head w/ my netmap code) i suspect that the difference in performance has to do with the PCIe controller. just for the records: the AMD motherboard works fine and can reach 14.88Mpps, i was just doing a couple of mistakes in my AMD tests, including the use of a slot with 16x form factor but only 4 lanes connected. This said, the i7-870 is about twice as fast as the Athlon II X4-635 in generating packets for the same clock speed. I think the different cache size might have some impact on the result given the Athlon has no L3 cache and the test program surely overflows the 512k L2 cache (i am using a total of 8k packet buffers, touching 64 bytes each for the payload, plus 24 bytes each for descriptors). Unfortunately at these speeds even small things matter a lot! cheers luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff
- John Baldwin's Original Message -
On Friday, June 10, 2011 11:00:15 am John wrote:
- John Baldwin's Original Message -
On Thursday, June 09, 2011 2:11:16 am Andriy Gapon wrote:
on 09/06/2011 01:30 John said the following:
Sorry John, here's the verbose dmesg output with your patch applied.
This is at the tail of the console:
pcib1: allocated memory range (0xf600-0xf6ff) for rid 10 of
pci0:1:3:0
map[14]: type I/O Port, range 32, base 0x4400, size 8,
enabled
pcib1: failed to allocate initial I/O port window
(0x4000-0x4fff,0x1000)
map[18]: type Memory, range 32, base 0xf5ff, size 12,
enabled
Output ends with a single 'M', not MCA as earlier.
Just a wild guess - what happens if you revert r222537 (you might need
to revert
r222804 first)?
I think he's getting a MCA due to writing to a bad address and getting a
PCI-e target abort equivalent and that the screen output is broken
because the VGA device is what is probably getting hosed by the pcib
driver.
Given that, I doubt the printf changes are related.
Just for grins, I decided to completely remove usb from the kernel
to see if it might help. Nolonger prints the MCA and/or M, just
hangs while printing out the no driver attached messages. Still
prints out the failed to allocate messages...
Hmmm. Your case is a bit different. PCI-PCI bridges have to allocate I/O
space on 4KB boundarys, so the smallest chunk it can allocate for the
resources behind your bridge is 0x4000-0x4fff which is what keeps failing.
Hmm, it's claiming that brgphy1 has some I/O ports that conflict allocated.
That makes no sense. brgphy devices have no I/O port resources. I think
the device_t got reused.
Can you try this perhaps to get started relative to sys/x86/x86/nexus.c:
In the following line, did by chance you want 'child' instead of dev?
bus_child_pnpinfo_str(dev, buf, 1024);
/usr/src.2011-06-10_22.00_EST/sys/x86/x86/nexus.c: In function
'nexus_alloc_resource':
/usr/src.2011-06-10_22.00_EST/sys/x86/x86/nexus.c:403: error: 'dev' undeclared
(first use in this function)
/usr/src.2011-06-10_22.00_EST/sys/x86/x86/nexus.c:403: error: (Each undeclared
identifier is reported only once
/usr/src.2011-06-10_22.00_EST/sys/x86/x86/nexus.c:403: error: for each function
it appears in.)
Thanks!
Index: nexus.c
===
--- nexus.c (revision 222932)
+++ nexus.c (working copy)
@@ -388,6 +388,27 @@ nexus_alloc_resource(device_t bus, device_t child,
if (rm == NULL)
return (NULL);
+ /* XXX: Hack */
+ if (type == SYS_RES_IOPORT start = 0x4000 start = 0x4) {
+ char *buf;
+
+ device_printf(bus, allocating range %#lx-%#lx for child,
+ start, end);
+ if (device_get_nameunit(child) != NULL)
+ printf( %s, device_get_nameunit(child));
+ printf( of %s\n, device_get_nameunit(
+ device_get_parent(child)));
+ buf = malloc(1024, M_DEVBUF, M_WAITOK);
+ *buf = '\0';
+ bus_child_pnpinfo_str(dev, buf, 1024);
+ if (*buf != '\0')
+ printf(\t%s\n, buf);
+ *buf = '\0';
+ bus_child_location_str(dev, buf, 1024);
+ if (*buf != '\0')
+ printf(\tat %s\n, buf);
+ free(buf, M_DEVBUF);
+ }
rv = rman_reserve_resource(rm, start, end, count, flags, child);
if (rv == 0)
return 0;
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
