Re: Reprobing of devices after module load?
On 11/21/11, John Baldwin j...@freebsd.org wrote: On Friday, November 18, 2011 11:48:20 am Paul B. Mahol wrote: Hi, Is there nice way in FreeBSD to force reprobe of devices for specific driver like it is done when kernel module is loaded (via DRIVER_MODULE(...) stuff)? Note that those probes happen for specific buses rather than for specific drivers. The routine that does this currently is static (devclass_driver_added() in sys/kern/subr_bus.c). What specific problem are you trying to solve? You might be able to use BUS_DRIVER_ADDED() or device_probe_and_attach() to achieve what you are trying to do. I have changed NDISulator to load 3rd party *.SYS from userspace via ioctl on /dev/ndis. For now i can do reprobe by reloading if_ndis.ko module. Loading if_ndis.ko ideally should not cause reprobe but reprobe should be done after ioctl on /dev/ndis. Perhaps devclass_add_driver from sys/kern/subr_bus can do 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
Reprobing of devices after module load?
Hi, Is there nice way in FreeBSD to force reprobe of devices for specific driver like it is done when kernel module is loaded (via DRIVER_MODULE(...) stuff)? ___ 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: cardbus and kldunload issue
On Sat, Feb 26, 2011 at 4:25 PM, Bernhard Schmidt bschm...@freebsd.org wrote: Hi, while working on a wireless driver for a Cardbus card I stumbled over an issue which bugs me quite a bit. The device: % none3@pci0:22:0:0: class=0x028000 card=0x107f1043 chip=0x02011814 rev=0x01 hdr=0x00 Loading the module attaches nicely to the device: # kldload if_ral % ral0: Ralink Technology RT2560 mem 0xf480-0xf4801fff irq 16 at device 0.0 on cardbus0 % ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 % ral0: [ITHREAD] # pciconf -l % ral0@pci0:22:0:0: class=0x028000 card=0x107f1043 chip=0x02011814 rev=0x01 hdr=0x00 Though, kldunload doesn't detach the device, it doesn't even call the module's detach function. # kldunload if_ral # pciconf -l % ral0@pci0:22:0:0: class=0x028000 card=0x107f1043 chip=0x02011814 rev=0x01 hdr=0x00 # kldstat % Id Refs Address Size Name % 1 27 0x8010 e640a0 kernel # ifconfig ral0 % ral0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 % ether 00:0e:a6:a6:1b:70 % media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) % status: no carrier And of course trying to use the device at that point will result in instant panics. Playing around a bit I've noticed that changing the bus name in: % DRIVER_MODULE(ral, pci, ral_pci_driver, ral_devclass, 0, 0); from pci to cardbus makes a big difference. On module unload the detach function is then called as expected. So, question is, are we doing some too strict checks on module unload while matching the bus? Or is this expected behavior and the drivers are supposed to indiciated that they support both pci and cardbus? I don't see the later anywhere in tree. There is MODULE_DEPEND(), if_ndis depends on pccard, pci and usb modules and use both MODULE_DEPEND() and DRIVER_MODULE() with them. If I'm not mistaken pccard depends on cardbus. ___ 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: [CFR] a small change of ifconfig(8)
On 11/25/10, Weongyo Jeong weongyo.je...@gmail.com wrote: Hello all, I'm sending this email to check whether my approach is reasonable that I added 2 line into ifconfig(8) to skip IFT_USB interfaces as follows: + if (sdl != NULL sdl-sdl_type == IFT_USB) + continue; And as additionally I added two changes of USB pf to call if_up(ifp) / if_down(ifp) explicitly to UP usbus interfaces though normally it always should be called through user ioctl calls. The reason why I make this patch is that I encountered a side-effect output from ifconfig(8) after USB packet filter is committed. Yes usbus interfaces are printed. Please give me some hints whether the patch is reasonable. If it's reasonable, is there other tools which I should make patches? Currently ifconfig will with special rc.conf configuration hang after boot making multiuser mode impossible to happen. Perhaps ifconfig tries to do something fancy with usbus interfaces. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 11/22/10, Alberto Villa avi...@freebsd.org wrote: On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote: Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. ok. unfortunately in this test i made an error and just saw that... `-- git status # On branch ndis5 # Your branch is ahead of 'origin/ndis5' by 13 commits. i hope it's ok for this time Git status should be empty. Just pull again. Or clone repo again, or do not use git and fetch tar.gz from site. I did some changes with forced rebase so that happened. When you say what you did be more specific, like are you are using i386 or amd64, and so on. FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r215448M: Thu Nov 18 08:34:00 CET 2010 r...@echo.hoth:/usr/obj/usr/src/sys/HPDV6 amd64 my kernel configuration file is a GENERIC trimmed down to the minimum (so that everything possible is loaded as a module) amd64, I see. And another broadcom card on CURRENT and on amd64 just panics, but this is another driver. Can you post link to your driver? For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. i did it, and here you are the results: http://pastebin.ca/1998450 http://pastebin.ca/1998454 Why it picked MAC first time without problems, otherwise ndis0 would never attach, and second time it reports error? For a moment disable wpa_supplicant in your rc.conf. And try to get scan results via ifconfig(8). like this: # ifconfig wlan0 destroy # ifconfig wlan create wlandev ndis0 # ifconfig wlan0 up # ifconfig wlan0 list scan And upload relevant dmesg output (ndis/NDIS lines) somewhere. And/or contact me off-list. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 11/22/10, Paul B Mahol one...@gmail.com wrote: On 11/22/10, Alberto Villa avi...@freebsd.org wrote: On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote: Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. ok. unfortunately in this test i made an error and just saw that... `-- git status # On branch ndis5 # Your branch is ahead of 'origin/ndis5' by 13 commits. i hope it's ok for this time Git status should be empty. Just pull again. Or clone repo again, or do not use git and fetch tar.gz from site. I did some changes with forced rebase so that happened. When you say what you did be more specific, like are you are using i386 or amd64, and so on. FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r215448M: Thu Nov 18 08:34:00 CET 2010 r...@echo.hoth:/usr/obj/usr/src/sys/HPDV6 amd64 my kernel configuration file is a GENERIC trimmed down to the minimum (so that everything possible is loaded as a module) amd64, I see. And another broadcom card on CURRENT and on amd64 just panics, but this is another driver. Can you post link to your driver? For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. i did it, and here you are the results: http://pastebin.ca/1998450 http://pastebin.ca/1998454 Why it picked MAC first time without problems, otherwise ndis0 would never attach, and second time it reports error? For a moment disable wpa_supplicant in your rc.conf. And try to get scan results via ifconfig(8). like this: # ifconfig wlan0 destroy # ifconfig wlan create wlandev ndis0 # ifconfig wlan0 up # ifconfig wlan0 list scan And upload relevant dmesg output (ndis/NDIS lines) somewhere. And/or contact me off-list. I managed to fix panic on amd64 for driver I'm using. So try the latest version. ___ 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: net.link.log_link_state_change broken?
On 11/19/10, Paul B Mahol one...@gmail.com wrote: On 11/18/10, Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: On Tue, 2 Nov 2010, Paul B Mahol wrote: Hi, It appears we do not log such events anymore (at least with wlan devices) in console. I set this sysctl to 0 via sysctl.conf, if I set it to 1, nothing will change. Because I had loging disabled for very long time I encountered this problem just now. not sure. Might be, might not be. Have you further looked into this? I at least see: ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_UP); ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_DOWN); That part is not problematic, klog part is. Messages of link state changes are not available in console but are available in klog and in console once you open it with cat. Reading comment it appears that logic is inverted in code. kern.consmute=0 caused link state change to never appear (even in dmesg) ... ___ 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: net.link.log_link_state_change broken?
On 11/21/10, Paul B Mahol one...@gmail.com wrote: On 11/19/10, Paul B Mahol one...@gmail.com wrote: On 11/18/10, Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: On Tue, 2 Nov 2010, Paul B Mahol wrote: Hi, It appears we do not log such events anymore (at least with wlan devices) in console. I set this sysctl to 0 via sysctl.conf, if I set it to 1, nothing will change. Because I had loging disabled for very long time I encountered this problem just now. not sure. Might be, might not be. Have you further looked into this? I at least see: ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_UP); ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_DOWN); That part is not problematic, klog part is. Messages of link state changes are not available in console but are available in klog and in console once you open it with cat. Reading comment it appears that logic is inverted in code. kern.consmute=0 caused link state change to never appear (even in dmesg) ... ^kern.consmute=1 ___ 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: tmpfs out of space (ZFS related?)
On Sun, Nov 21, 2010 at 10:42 PM, Ivan Voras ivo...@freebsd.org wrote: On 11/21/10 23:19, Eir Nym wrote: On 22 November 2010 01:00, Eir Nymeir...@gmail.com wrote: On 22 November 2010 00:47, Bruce Cranbr...@cran.org.uk wrote: On Mon, 22 Nov 2010 00:43:03 +0300 Eir Nymeir...@gmail.com wrote: Which type of MFS do you use? I think you shold use swap-backed for your /tmp, not malloc-based. Last type is only for in-kernel file system. It's tmpfs(5), not md(4). I wonder if you can create FIFO and sockets with md(4). md(4) is geometry, not filesystem. md is a GEOM class which presents several types of devices backed by virtual memory. You can create file systems on top of those and mount them. The downside is that each of those layers has its own copy of the original data (and them some). tmpfs OTOH is a real memory file system, without the need for a backing device, and it is more efficient with respect to data copies (not perfect - it still AFAIK has to maintain something like 2 copies). AFAIK, if this was ever correct it is not any more. Data copies can mean anything. I use 1.5 GB file in tmpfs on 2GB RAM and 0B SWAP without problems. tmpfs(5) doesn't support this file types as I can see in FreeBSD source code. Maybe it is handled by default code, but they are supported. I have used tmpfs extensively for the last few years for mostly static servers (i.e. /tmp contains some sockets, a small number of short-lived temporary files, etc) - and it so far worked very well. This is actually the first time it failed me in some way. It can be anything: overflow, race, memory corruption ... Find way to reproduce it 100%. ___ 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: net.link.log_link_state_change broken?
On 11/18/10, Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: On Tue, 2 Nov 2010, Paul B Mahol wrote: Hi, It appears we do not log such events anymore (at least with wlan devices) in console. I set this sysctl to 0 via sysctl.conf, if I set it to 1, nothing will change. Because I had loging disabled for very long time I encountered this problem just now. not sure. Might be, might not be. Have you further looked into this? I at least see: ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_UP); ./net80211/ieee80211_freebsd.c: if_link_state_change(ifp, LINK_STATE_DOWN); That part is not problematic, klog part is. Messages of link state changes are not available in console but are available in klog and in console once you open it with cat. Reading comment it appears that logic is inverted in code. ___ 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: panic: loading if_bfe after boot
On Fri, Nov 19, 2010 at 1:29 AM, Pyun YongHyeon pyu...@gmail.com wrote: On Sat, Oct 30, 2010 at 09:19:06PM -0700, Pyun YongHyeon wrote: On Sat, Oct 30, 2010 at 5:40 PM, Paul B Mahol one...@gmail.com wrote: Hi, Loading if_bfe module after boot hangs machine, it works/attach fine from loader. Tell me if you need bt. Yes, I want to see the back trace. I think it was fixed in HEAD(r215348) and MFCed to stable/8 and stable/7. Of course it did. Otherwise I would scream on list ;) ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 11/17/10, Alberto Villa avi...@freebsd.org wrote: On Mon, Nov 15, 2010 at 2:41 PM, Paul B Mahol one...@gmail.com wrote: Feel free to test code at: gitorious.org/NDISulator github.com/richardpl/NDISulator The code is developed on CURRENT. But with small changes it can be compiled on STABLE too. thanks! i've applied a checkout of last night to current. i can load the module after boot, but the panic is still there when i unload or load on boot, and wpa_supplicant fails to work (see attached log) Just now I have only one tester (and that is without counting me). consider me as the third one :) Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. When you say what you did be more specific, like are you are using i386 or amd64, and so on. When testing, enable debug.bootverbose, and debug.ndis sysctl before loading miniport module. [miniport module is module you created with ndisgen(8)] Do not load miniport module(s) during boot(from loader), if it ever worked it was big luck. [Even on Windows, drivers are loaded after boot.] Actually drivers can be loaded but we must be extra carefull what to call during boot and what to call after boot. For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 11/15/10, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 3:36 PM, Paul B Mahol one...@gmail.com wrote: Currently amd64 is broken with some/most drivers. Drivers appears to use fpu registers. I dunno how it ever worked, probably original developer(s) never encountered drivers which use fpu registers. I will probably fix amd64 support in this year. so, i've tried the ndis driver with amd64 and it paniced, as you said. do you have any idea on when you're gonna fix this? i need to know if i can keep amd64 and wait for a fix (in short time) or if i have to install i386 temporarily... Feel free to test code at: gitorious.org/NDISulator github.com/richardpl/NDISulator The code is developed on CURRENT. But with small changes it can be compiled on STABLE too. Just now I have only one tester (and that is without counting me). ___ 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: Ctrl-alt-delete in syscons pause/scrollback mode breaks system
On 11/6/10, Bruce Cran br...@cran.org.uk wrote: Today I came back to my computer and realised I'd left ttyv0 in history/scrollback mode, with scroll-lock enabled. To see what would happen I pressed Ctrl-Alt-Delete to reboot and was surprised to see that it seemed to get partway through the process but it never rebooted: the other ttys were killed and I could still break into the debugger but otherwise the system was unresponsive. Trying to repeat it after rebooting I ended up with a system that won't even break into the debugger. Is this expected? Last issue, was reported my me long ago and only workaround was commited, which actually did not solved problem for me. I'm still looking forward for complete syscons rewrite. ___ 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: panic: invalid PDPE on recend amd64
On 11/6/10, Jia-Shiun Li jiash...@gmail.com wrote: Hi, I got a similar panic on amd64. Looking into the source it hit KASSERT((base (len - 1))) in pmap_demote_DMAP(). I replaced it with a printf to see what triggered the assertion and here is the output. Combined with memcontrol output 'bogus' keyword it seems buggy BIOS violated some kind of spec and caused this. Is it fatal? It looks fine on my machine without the assertion. Send uname output. The fix for this issue got commited few days ago. ___ 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
net.link.log_link_state_change broken?
Hi, It appears we do not log such events anymore (at least with wlan devices) in console. I set this sysctl to 0 via sysctl.conf, if I set it to 1, nothing will change. Because I had loging disabled for very long time I encountered this problem just now. ___ 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: wpa_supplicant gets points for trying, I suppose....
On 11/1/10, David Wolfskill da...@catwhisker.org wrote: FreeBSD 9.0-CURRENT #31 r214621M Nov 1 15:09:40 d130 wpa_supplicant[569]: Failed to initiate AP scan. Nov 1 15:10:10 d130 last message repeated 3 times Nov 1 15:10:50 d130 last message repeated 4 times ... Nov 1 15:11:00 d130 wpa_supplicant[569]: Failed to initiate AP scan. Nov 1 15:11:10 d130 wpa_supplicant[569]: Failed to initiate AP scan. ... Nov 1 15:11:20 d130 wpa_supplicant[569]: Failed to initiate AP scan. Nov 1 15:11:30 d130 wpa_supplicant[569]: Failed to initiate AP scan. ... Nov 1 15:11:40 d130 wpa_supplicant[569]: Failed to initiate AP scan. ... Nov 1 15:11:50 d130 wpa_supplicant[569]: Failed to initiate AP scan. Nov 1 15:12:10 d130 last message repeated 2 times Nov 1 15:14:10 d130 last message repeated 12 times I have the switch on this laptop in position to disable the wireless device (iwn(4)). Is there some way wpa_supplicant (or something) might be able to recognize that this is a pointless exercise? Well iwn could bring device down when radio is turned off and bring it up when radio is turned on ??? I don't recall stable/8 doing this, though I could be wrong. ___ 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
panic: invalid PDPE on recend amd64
Hi, Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE This is on: Copyright (c) 1992-2010 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 9.0-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 root@:/usr/obj/usr/src/sys/kernel i386 CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbffFPU,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=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2087346176 (1990 MB) ACPI APIC Table: HP 30A2 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard acpi0: HPQOEM SLIC-MPC on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed ___ 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: panic: invalid PDPE on recend amd64
On 10/30/10, Andriy Gapon a...@icyb.net.ua wrote: on 30/10/2010 17:43 Paul B Mahol said the following: Hi, Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE This is on: Copyright (c) 1992-2010 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 9.0-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 root@:/usr/obj/usr/src/sys/kernel i386 amd64 or i386? That is working i386 kernel, I can send bt of amd64 kernel as picture. CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbffFPU,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=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2087346176 (1990 MB) ACPI APIC Table: HP 30A2 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard acpi0: HPQOEM SLIC-MPC on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed It seems that the panic happens at the stage where you should be able to enter ddb and obtain a backtrace at the very least, after adding DDB option to your kernel. ___ 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: panic: invalid PDPE on recend amd64
On 10/30/10, Paul B Mahol one...@gmail.com wrote: On 10/30/10, Andriy Gapon a...@icyb.net.ua wrote: on 30/10/2010 17:43 Paul B Mahol said the following: Hi, Booting amd64 kernel panic in pmap_demote_DMAP(): invalid PDPE This is on: Copyright (c) 1992-2010 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 9.0-CURRENT #1 r214542+ac89f9b: Sat Oct 30 09:40:45 UTC 2010 root@:/usr/obj/usr/src/sys/kernel i386 amd64 or i386? That is working i386 kernel, I can send bt of amd64 kernel as picture. CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6f2 Family = 6 Model = f Stepping = 2 Features=0xbfebfbffFPU,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=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2010NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2087346176 (1990 MB) ACPI APIC Table: HP 30A2 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard acpi0: HPQOEM SLIC-MPC on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed It seems that the panic happens at the stage where you should be able to enter ddb and obtain a backtrace at the very least, after adding DDB option to your kernel. panic: pmap_demote_DMAP: Invalid PDPE cpuid=0 KDB: enter: panic: [ thread pid 0 tid .. Stopped at .. db bt Tracing pid 0 .. kdb_enter() .. panic() .. pmap_demote_DMAP() .. amd64_mrinit() .. mem_modevent() .. module_register_init() .. mi_startup() .. If I remove mem module from loader.conf kernel boots fine. If I kldload mem after boot, panic happens. ___ 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
panic: loading if_bfe after boot
Hi, Loading if_bfe module after boot hangs machine, it works/attach fine from loader. Tell me if you need bt. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel swhet...@gmail.com wrote: On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz g...@unixarea.de wrote: I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=WPA DHCP wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? The problem is that the Broadcom NDIS driver is generating connection events, but nothing is relaying that information to the wpa_supplicant daemon. Since the wpa_supplicant daemon doesn't see a connection event, it retries connecting I had created a patch in PR 113915 which solves this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=113915 Give it a try, if it solves your problem submit a followup to the PR. Hmm, ndis_events are required if you use -Dndis and wpa/rsn and need to get event of PMKIDs. For other uses it is of no use. Try -Dbsd driver for wpa_supplicant with code from here: Try http://gitorious.org/ndisulator ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 10/28/10, Matthias Apitz g...@unixarea.de wrote: El dia Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribio: On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol one...@gmail.com wrote: NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. i've tried that driver, but apparently it doesn't support my card... loading the .ko doesn't show anything... Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Following Scot's hint (thanks for this) I downloaded today morning the WinXP x86 driver zip archive from www.Acer.com and built the bcmwl5_sys.ko with ndisgen(8). The system panics on early boot stages when the kmod was pulled in via loader.conf. Newer drivers do that, I don't have solution. If the system is up, you can kldload the module fine and the interface ndis0 appears and even the card gets associated with the AP (i.e. wpa_supplicant(8) must work fine). The ifconfig(8) shows the interface as: ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 90:4c:e5:00:06:ce media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated and the Wifi indicator light of the laptop is green. But: # dhclient ndis0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument ndis0: not found and the same is with # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. But note that such old CURRENT have few bugs in NDISulator. For example scan results are incomplete and scanning can trigger panic in some situations. If you use wpa_supplicant -Dndis you will never encounter such problems. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 10/27/10, Alberto Villa avi...@freebsd.org wrote: On Tue, Oct 26, 2010 at 2:09 PM, Paul B Mahol one...@gmail.com wrote: i've tried ndis without success... Sharing you experience would help (if you are not on amd64). i'm on i386 at the moment, but i'll switch to amd64 as soon as i decide what to do (keep freebsd natively or virtualize it under windows... it depends on the wireless driver). would that change anything? Currently amd64 is broken with some/most drivers. Drivers appears to use fpu registers. I dunno how it ever worked, probably original developer(s) never encountered drivers which use fpu registers. I will probably fix amd64 support in this year. here's my experience. also, as a reference, here's what i get if i add the device id to siba_bwn: # kldload if_bwn siba_bwn0: Broadcom BCM43225 802.11b/g/n Wireless mem 0xda10-0xda103fff irq 16 at device 0.0 on pci2 siba_bwn0: cannot map register space device_attach: siba_bwn0 attach returned 6 and here is the new open source driver: http://wireless.kernel.org/en/users/Drivers/brcm80211 and now, ndis. the driver is bcmwl6 (http://people.freebsd.org/~avilla/bcmwl6.inf and http://people.freebsd.org/~avilla/bcmwl6.sys , apparently no need for firmware files, but i'm not sure), which is said not to work with ndis on linux forums (maybe they removed the support for winxp) matthias: you should try bcmwl5, that could work for you using the unmodified files i've attached (they default to winvista and win7) i get this: # kldload ./bcmwl6_sys.ko module ndis already present! no match for NdisMIndicateReceiveNetBufferLists no match for NdisFreeNetBufferListPool no match for NdisMRegisterScatterGatherDma no match for NdisMAllocatePort no match for NdisQueueIoWorkItem no match for NdisMFreePort no match for NdisMOidRequestComplete no match for NdisMNetPnPEvent no match for NdisAllocateIoWorkItem no match for NdisFreeIoWorkItem no match for NdisGetVersion no match for NdisMSetMiniportAttributes no match for NdisMDeregisterMiniportDriver no match for NdisAllocateTimerObject no match for NdisMPauseComplete no match for NdisOpenConfigurationEx no match for NdisFreeTimerObject no match for NdisCancelTimerObject no match for NdisSetTimerObject no match for NdisMSynchronizeWithInterruptEx no match for NdisMDeregisterInterruptEx no match for NdisMRegisterInterruptEx no match for NdisMIndicateStatusEx no match for NdisFreeNetBufferList no match for NdisGetSystemUpTimeEx no match for NdisAllocateMdl no match for NdisAllocateNetBufferAndNetBufferList no match for NdisFreeMdl no match for NdisMResetComplete no match for NdisMSendNetBufferListsComplete no match for NdisAllocateNetBufferListPool no match for NdisMRegisterMiniportDriver no match for NdisMDeregisterScatterGatherDma no match for NdisAllocateMemoryWithTagPriority no match for NdisMGetBusData no match for NdisMSetBusData no match for ZwQueryInformationFile no match for ZwReadFile no match for ZwCreateFile no match for ExFreePoolWithTag no match for IoRegisterPlugPlayNotification no match for IoUnregisterPlugPlayNotification NDIS dummy called... NDIS dummy called... which should mean that the driver doesn't support xp. so i tried changing (in the .inf) %V_BCM% = BROADCOM, NTx86.6.0, NTamd64.6.0, NTx86.6.1, NTamd64.6.1 Now when you mention this I may send patch for ndisgen(8) so it will deny creating modules for 6.X API drivers. to %V_BCM% = BROADCOM, NTx86, NTamd64 and then i only get module ndis already present!, but no interface shows up i also tried removing NTx86, making it %V_BCM% = BROADCOM, NTamd64 (it should be correct), and with this modification i get the same error messages of the first attempt anyway i don't have any experience with ndis... should i test anything else? NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. ___ 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: Broadcom BCM4310 USB Controller (Wifi)
On 10/26/10, Alberto Villa avi...@freebsd.org wrote: On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz g...@unixarea.de wrote: I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the above chip is still not supported. I am wrong? i have the same problem with a BCM43225. there is a linux driver: is anyone going to port it in the near future? would a donation help the process? Any other idea how to get Wifi working on this mini laptop? i've tried ndis without success... Sharing you experience would help (if you are not on amd64). ___ 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: [RFC] More meaningful information about ENOEXEC for kldload(8)
On 10/25/10, Xin LI delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Here is a simple patch that adds more meaning messages when kldload hits ENOEXEC. Before patch: kldload: can't load geom_eli.ko: Exec format error After patch: kldload: can't load geom_eli.ko: Exec format error kldload: Dependendent kernel module cannot be loaded from kern.module_path? Comments? What about modules built for different __FreeBSD_version ? ___ 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: panic on kthread_exit under INVARIANTS
On 10/12/10, David Xu davi...@freebsd.org wrote: Paul B Mahol wrote: Hi, If kernel threads were created via kproc_kthread_add() when last kernel thread exits it will trigger panic. It panics in queue.h probably introduced with rec I have committed a patch, can you try it ? http://svn.freebsd.org/changeset/base/213714 Yes, panic doesn't happen any more. ___ 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
panic on kthread_exit under INVARIANTS
Hi, If kernel threads were created via kproc_kthread_add() when last kernel thread exits it will trigger panic. It panics in queue.h probably introduced with recent commit. ___ 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: Move banner to games
On 10/7/10, army.of.root army.of.r...@googlemail.com wrote: On 10\10\02 18:48, Paul B Mahol wrote: On 10/2/10, Brandon Goochjamesbrandongo...@gmail.com wrote: On Sat, Oct 2, 2010 at 7:36 AM, Paul B Maholone...@gmail.com wrote: Hi, I see no point to have it in usr/bin. Cool! This is the first time I've heard of this program! How come the folks at my university who manage the line printers have never let me on to this?! Ahh -- wait a sec -- I'm beginning to see your point about the whole move it to games thing... -Brandon aka The Green Bar Bandit NetBSD and OpenBSD have this version in games and horizontal version of banner in usr/bin. I see no point to have this program(s) in base at all. I will just stop here. Hi, A horizontal version of banner could be nice for motd etc. I like banner. It makes me smile and think that FreeBSD is a cosy place to be. have a nice day :) You have figlet and toilet with other sundry amusements in ports. ___ 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
Move banner to games
Hi, I see no point to have it in usr/bin. ___ 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: Move banner to games
On 10/2/10, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Oct 2, 2010 at 7:36 AM, Paul B Mahol one...@gmail.com wrote: Hi, I see no point to have it in usr/bin. Cool! This is the first time I've heard of this program! How come the folks at my university who manage the line printers have never let me on to this?! Ahh -- wait a sec -- I'm beginning to see your point about the whole move it to games thing... -Brandon aka The Green Bar Bandit NetBSD and OpenBSD have this version in games and horizontal version of banner in usr/bin. I see no point to have this program(s) in base at all. I will just stop here. ___ 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: Sleep/Lenovo SL410
On 10/1/10, Ian Smith smi...@nimnet.asn.au wrote: On Thu, 30 Sep 2010, Matt wrote: Success! After setting every possible suspend/resume sysctl, sysctl hw.pci.do_power_resume=0 allowed suspend and resume. Still beeps 1-3 times before suspend, with rapid sleep light flashing until suspend complete. Interesting; $someone may document do_power_resume a bit more $someday? It is already documented. Kernel conf is attached. World built from last Friday's CVS, -CURRENT acpiconf -s3 works perfectly from console previously opened windows are garbled until refresh in X Some thinkpads have responded positively in this regard to setting hw.syscons.sc_no_suspend_vtswitch=1 acpiconf -s4 causes shutdown, does not resume on power on. Suspend To Disk is not expected to work; your laptop (like most) has no BIOS support for S4, as per your hw.acpi.s4bios: 0 Suspend to disk does not work because FreeBSD does not support it. (s4bios is irrelevant here) ___ 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: Clang now builds world and kernel, on i386 and amd64
On 9/22/10, Dimitry Andric d...@freebsd.org wrote:
Hi,
As of r212979, you should now be able to build world and kernel on i386
and amd64 with clang, without any additional patches!
To do so, make sure you have updated your installed world to at least
r212904 (which has the most recently imported clang/llvm snapshot), and
put the following in /etc/src.conf:
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
Both world and kernel can also be installed, and should run properly,
but please make sure you have a way to revert if anything unexpected
happens. :) Alternatively, just install into a chroot to try it out
from there.
Some additional information can be found on this wiki page:
http://wiki.freebsd.org/BuildingFreeBSDWithClang
Thanks to all the people that made this possible, especially Roman
Divacky, Ed Schouten, Rui Paulo, and of course the clang/llvm
developers.
When to expect to get rid of GNU as and other binutils tools?
___
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: ISO9660 4GB directory structures boundary limit and growisofs
On 4/19/10, Paul B Mahol one...@gmail.com wrote: On 4/19/10, Tom Evans tevans...@googlemail.com wrote: On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. That is pretty old, from 2.4 era, it was added after it was found that isofs had bug. Windows at least try to show something - only one session, but fourth and not second session crossed 4GB limit. The source also claims that in BD case there is no need for _force_ switch at all. Mounting with -norrip shows all sessions. Kernel displays RRIP without PX field? if I try to mount normal way. ___ 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: ISO9660 4GB directory structures boundary limit and growisofs
On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. ___ 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: ISO9660 4GB directory structures boundary limit and growisofs
On 4/19/10, Tom Evans tevans...@googlemail.com wrote: On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol one...@gmail.com wrote: On 4/17/10, Paul B Mahol one...@gmail.com wrote: On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. Update: Linux shows all sessions and Windows 7 shows only first one. From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. That is pretty old, from 2.4 era, it was added after it was found that isofs had bug. Windows at least try to show something - only one session, but fourth and not second session crossed 4GB limit. The source also claims that in BD case there is no need for _force_ switch at all. ___ 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: ISO9660 4GB directory structures boundary limit and growisofs
On 4/17/10, Andriy Gapon a...@icyb.net.ua wrote: on 17/04/2010 02:07 Paul B Mahol said the following: Hi, It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Is it expected that everyone knows what -use-the-force-luke=4gms is? Should we allow it like linux does? What exactly is disallowed on FreeBSD? http://fy.chalmers.se/~appro/linux/DVD+RW/ search for 4gms :) ___ 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: ISO9660 4GB directory structures boundary limit and growisofs
On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle kient...@freebsd.org wrote: Paul B Mahol wrote: It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? Are you claiming there is a problem when FreeBSD reads such images or a problem with creating such images? What programs are you using? I burn flac files in multiple sessions, each session have separate directory, on DVD+R DL MKM/003 After I used 4gms switch mounted fs shows nothing. (but there is 5GB of data) According to growisofs source BD (bluray) dont need this switch at all ... This sounds like a pretty unsurprising 32-bit truncation bug: the filesystem structures in ISO9660 are all sector numbers so 8TB should be the natural limit (4G sectors times 2k bytes/sector). I did not tested this on FreeBSD amd64 yet. ___ 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
ISO9660 4GB directory structures boundary limit and growisofs
Hi, It is apparently not possible to make use of -use-the-force-luke=4gms on FreeBSD when appending new session after 4GB. Mounted disk afterwards show nothing. Should we allow it like linux does? ___ 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: newfs_msdos and DVD-RAM
On 4/2/10, Andriy Gapon a...@freebsd.org wrote:
on 02/04/2010 22:26 Andriy Gapon said the following:
OK, I did it again.
I tested the below patch using the scenario described above.
Could you please review and/or test this patch?
If you like it and it works, I can commit it.
Thanks!
--- a/sbin/newfs_msdos/newfs_msdos.c
+++ b/sbin/newfs_msdos/newfs_msdos.c
@@ -427,6 +427,9 @@ main(int argc, char *argv[])
if (bpb.bpbBytesPerSec MINBPS)
errx(1, bytes/sector (%u) is too small; minimum is %u,
bpb.bpbBytesPerSec, MINBPS);
+bpb.bpbSecPerClust /= (bpb.bpbBytesPerSec / MINBPS);
+if (bpb.bpbSecPerClust == 0)
+bpb.bpbSecPerClust = 1;
if (!(fat = opt_F)) {
if (opt_f)
fat = 12;
And here is a safer one (in case of a huge sector size 32KB).
I will appreciate any testing with real media that you might have.
diff --git a/sbin/newfs_msdos/newfs_msdos.c b/sbin/newfs_msdos/newfs_msdos.c
index 955c3a5..3f2778d 100644
--- a/sbin/newfs_msdos/newfs_msdos.c
+++ b/sbin/newfs_msdos/newfs_msdos.c
@@ -427,6 +427,12 @@ main(int argc, char *argv[])
if (bpb.bpbBytesPerSec MINBPS)
errx(1, bytes/sector (%u) is too small; minimum is %u,
bpb.bpbBytesPerSec, MINBPS);
+bpb.bpbSecPerClust /= (bpb.bpbBytesPerSec / MINBPS);
+if (bpb.bpbSecPerClust == 0)
+ bpb.bpbSecPerClust = 1;
+if (bpb.bpbSecPerClust * bpb.bpbBytesPerSec 32 * 1024)
+ errx(1, bytes per sector (%u) is greater than 32k,
+ bpb.bpbSecPerClust * bpb.bpbBytesPerSec);
if (!(fat = opt_F)) {
if (opt_f)
fat = 12;
Works for me, thanks!
(I will test compatibility with winXP later)
___
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: fsck unable to read disk sectors
On 3/29/10, Alexander Best alexbes...@wwu.de wrote: hi there, when doing fsck on my / fs i get this error: Cannot Read BLK. 471617640 and The Following Disk Sectors could not be read: 471617643. after this message the partition gets marked dirty. i performed the following steps to verify the problem: 1) dd if=/dev/ada0 of=/dev/null bs=1m 2) fsck / under freebsd 7 3) mount -u -o snapshot /.snap/snapshot1 / fsck_ffs /.snap/snapshot1 all three steps showed no problem with that harddrive whatsoever. also smartd doesn't complain about anything. i'm running HEAD (r205860) on amd64. this is the output of `dmesg -a|grep ada0`: ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 ada0: SAMSUNG SP2504C VT100-50 ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) Last time I tried ahci on dead disk it did not complained at all (usually I get dead LBA listed on console). ___ 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
newfs_msdos and DVD-RAM
Hi, FreeBSD 9.0 CURRENT panics when mounting file system created via newfs_msdos on DVD-RAM disc. Something to do about divide by zero. ___ 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: newfs_msdos and DVD-RAM
On Fri, Mar 19, 2010 at 7:11 PM, Fabian Keil freebsd-lis...@fabiankeil.de wrote: Paul B Mahol one...@gmail.com wrote: FreeBSD 9.0 CURRENT panics when mounting file system created via newfs_msdos on DVD-RAM disc. Something to do about divide by zero. I recently had a similar problem with a 16GB iPod. I still haven't managed to actually mount it, but the patch below at least works around the panic. Does it work for you, too? Obviously it will fix panic, but will not allow to mount. Zero value should be handled already much before. It looks the real bug is in newfs_msdos. For some reason I did not managed to format DVD-RAM disc with FAT32 on WinXP, it trashed disc completely so I was forced to blank it with dvd+rw-tools. ___ 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
