Re: bwn(4) on 8.1-RC1: connection problems
On Sun, Jun 20, 2010 at 2:23 PM, Quentin Stievenart wrote: > Hi, > > I've some broadcom wireless cards to test here (two BCM4318 and a > BCM4312). This week I tried the BCM4318 one (the 4312 is on a netbook, > I'll try it later, if the 4318 works some day). > > First of all, I was able to use it with ndisgen on FreeBSD 7.1, but > since the 7.2, it doesn't work anymore. So, two day ago I installed a > 8.1-RC1 and tried bwi(4), but a `ifconfig wlan0 scan` wasn't detecting > anything. > > So I gave bwn(4) a try, and it detect perfectly my network, but I just > can't connect to it, neither with dhclient nor with a static IP. > Here's what I do to try to connect: > > # kldload if_bwn > # kldload bwn_v4_ucode > # ifconfig wlan0 create wlandev bwn0 > # ifconfig wlan0 up > # ifconfig wlan0 ssid myssid channel 6 wepmode on wepkey mywepkey > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu > 1500 > ether 00:11:50:d0:2f:6f > media: IEEE 802.11 Wireless Ethernet DS/11Mbps mode 11b > status: associated > ssid myssid channel 6 (2437 MHz 11b) bssid 00:60:b3:7a:5c:29 > country US authmode OPEN privacy ON deftxkey UNDEF wepkey 1:40-bit > txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 > roam:rssi 7 roam:rate 1 wme > # ifconfig bwn0 > bwn0: flags=8843 metric 0 mtu 2290 > ether 00:11:50:d0:2f:6f > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > status: associated > > Then, for the static IP: > # ifconfig wlan0 inet 192.168.1.30 netmask 255.255.255.0 Where is weptxkey. Read manual again. > # route add default 192.168.1.1 > # arp -a > ? (192.168.1.30) at 00:11:50:d0:2f:6f on wlan0 permanent [ethernet] > > And I can't ping anything (except localhost and 192.168.1.30) > Or, with dhcp: > # dhclient wlan0 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > > Here's what pciconf -lv tells me about my card: > > siba_b...@pci0:2:2:0: class=0x028000 card=0x70011799 chip=0x431814e4 > rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'Broadcom 802.11b/g (BCM4318)' > class = network > > And a dmesg | egrep "(bwn|wlan)": > > siba_bwn0: mem 0xfdefc000-0xfdefdfff > irq 22 at device 2.0 on pci2 > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4318 rev 9) PHY (analog 3 type 2 rev 7) RADIO (manuf > 0x17f ver 0x2050 rev 8) > bwn0: DMA (32 bits) > bwn0: [FILTER] > wlan0: Ethernet address: 00:11:50:d0:2f:6f > bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) > wlan0: ieee80211_new_state_locked: pending INIT -> SCAN transition lost > wlan0: link state changed to UP > bwn0: need multicast update callback > bwn0: RX decryption attempted (old 0 keyidx 0) > bwn0: RX decryption attempted (old 0 keyidx 0) > bwn0: RX decryption attempted (old 0 keyidx 0) > bwn0: RX decryption attempted (old 0 keyidx 0) > bwn0: RX decryption attempted (old 0 keyidx 0) > > Also, when I start tcpdump on wlan0, and try to ping this computer from > another one, I see all the ping requests and responses on FreeBSD, but > the other computer don't get any response. > > Does anyone knows what to do now ? > > Regards, > > Quentin Stievenart. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Broadcom Wireless BCM4312 Rev.02 (BCM4310 UART) troubles
On Tue, Aug 31, 2010 at 10:30 AM, Michael BlackHeart wrote: > Hello > > I've got a problem with Broadcomm Wireless. > I have notebook HP Compaq 6720s with BCM4312. I disassemblied book and saw > there plugable Wireless Module but I'm lazy to do it again to werify it's > ID. > > Windows XP drivers works fine and says that is's > > PCI\VEN_14E4&DEV_4312&SUBSYS_1371103C&REV_02\4&29E2C51B&0&00E1 > MEMORY E400 - E4003FFF > IRQ 17 > > I've tried : > FreeBSD 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > And noting as i386 8.1 release. > > Now I'm running: > FreeBSD 8.1-STABLE FreeBSD 8.1-STABLE #0 r211991: Mon Aug 30 14:58:34 MSD > 2010 > root@:/usr/obj/usr/src/sys/GENERIC amd64 > > With no driver attached "pciconf -l -cvb" says: > > no...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4310 UART (Wireless Ethernet Adapter)' > class = network > bar [10] = type Memory, range 64, base 0xe400, size 16384, enabled > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 09[58] = vendor (length 120) > cap 05[e8] = MSI supports 1 message, 64 bit > cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > Clean install, trying bwi driver first > > cd /usr/ports/net/bwi-firmware-kmod && make install clean && rehash > kldload bwi_ucode_v3 > cd /usr/sys/src/modules/bwi > make all obj depend install clean > kldload if_bwi > > Aug 18 12:19:58 kernel: bwi0: > mem 0xe400-0xe4003fff irq 17 at device 0.0 on pci16 > Aug 18 12:19:58 kernel: bwi0: [ITHREAD] > Aug 18 12:19:58 kernel: bwi0: BBP: id 0x4311, rev 0x2, pkg 0 > Aug 18 12:19:58 kernel: bwi0: MAC rev 13 is not supported bwi(4) does not support your card. > Aug 18 12:19:58 kernel: bwi0: no MAC was found > Aug 18 12:19:58 kernel: device_attach: bwi0 attach returned 6 > > pciconf -l -cvb says: > > b...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4310 UART (Wireless Ethernet Adapter)' > class = network > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 09[58] = vendor (length 120) > cap 05[e8] = MSI supports 1 message, 64 bit > cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > now rebooting 'cos even after kldunloading if_bwi module it's still lists in > pciconfand trying bwn > > cd /usr/ports/net/bwn-firmware-kmod && make install clean && rehash > kldload bwn_v4_ucode.ko > kldload if_bwn > > pciconf -l -cvb says: > > siba_bwn0: mem 0xe400-0xe4003fff > irq 17 at device 0.0 on pci16 > siba_bwn0: unsupported coreid (USB 1.1 Host) > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf > 0x17f ver 0x2050 rev 2) > bwn0: DMA (64 bits) > bwn0: Using 1 MSI messages > bwn0: [FILTER] > > siba_b...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 > rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4310 UART (Wireless Ethernet Adapter)' > class = network > bar [10] = type Memory, range 64, base 0xe400, size 16384, enabled > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 09[58] = vendor (length 120) > cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > ifconfig bwn0 up scan > bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) > ifconfig: unable to get scan results > bwn0: status of RF switch is changed to OFF You must create wlanX first. > > book have a switch to turn on/off all radio and it's always on. also when > i'm switching it FreeBSD says nothing > Also I tried acpi_hp - no sense > And i didn't find any apropriate in sysctl > > Moving next - ndis > I've tried couple of drivers > With WinXP that running on drivers v. VERSION: 7.10 REV: B from sp41680 > And OS goes to kernel panic just when I kldloaded it. NDISulator on amd64 is mostly broken. It can panic on driver initialization (fixed in my git repo). Also fpudna in kernel mode can cause panic (not yet fixed). > No dump, sorry, but I don't think that it matters a thing > > Another one - VERSION: 6.10 REV: A from sp34152 works a bit better > It converts and loads without panic but in debug: > kldload bcmwl564_sys.ko > > ndis0: mem 0xe400-0xe4003fff irq 17 at > device 0. > 0 on pci16 > > ndis0: [ITHREAD] > > ndis0: NDIS API version: 5.1 > > fpudna in kernel mode! Interesting, that version of driver does not use symbols which cause crash on driver initialization of older driver... Of course most 6.X drivers dont have support for older NDIS 5.1 API. > pciconf -lcvb says: > nd...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 > hdr=0x00 > > vendor = 'Broadcom Corporation' > > device = 'BCM4310 UART (Wireless Ethernet Adapter)' > > class = network > > bar [10] = type Memory, range 64, base 0xe4
Re: cdrtools /devel and wodim broken
On 10/26/10, Jakub Lach wrote: > > > Joerg Schilling-3 wrote: >> >> wodim is a dead end from a 6 year old version of cdrecord with the DVD >> support >> ripped off and replaced by something broken. But there have been even more >> bugs >> added to wodim and it is not under "development" since May 2007. >> >> If cdrecord gives the same message, I encourage you to make a kernel bug >> report. >> This message is a hint to a serious kernel problem. A sense key value -1 >> cannot >> happen, so you need to find out why the SCSI command has not been >> transported >> correctly by the kernel. >> > > Hi Joerg. > > I usually prefer cdrtools, wodim was convenient way to > try old code. > > After booting GENERIC kernel + ahci driver and compiling > cdrtools release problem is still present. > > Full message. > > cdrecord: No write mode specified. > cdrecord: Assuming -sao mode. > cdrecord: If your drive does not accept -sao, try -tao. > cdrecord: Future versions of cdrecord may have different drive dependent > defaults. > Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) > 1995-2010 Joerg Schilling > TOC Type: 1 = CD-ROM > scsidev: '1,0,0' > scsibus: 1 target: 0 lun: 0 > Using libscg version 'schily-0.9'. > SCSI buffer size: 65536 > atapi: 0 > Device type: Removable CD-ROM > Version: 0 > Response Format: 2 > Capabilities : > Vendor_info: 'HL-DT-ST' > Identifikation : 'DVDRAM GSA-U20N ' > Revision : 'HX11' > Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. > Current: DVD-R sequential recording > Profile: DVD-RAM > Profile: DVD-R sequential recording (current) > Profile: DVD-R/DL sequential recording > Profile: DVD-R/DL layer jump recording > Profile: DVD-RW sequential recording > Profile: DVD-RW restricted overwrite > Profile: DVD+RW > Profile: DVD+R > Profile: DVD+R/DL > Profile: DVD-ROM > Profile: CD-R > Profile: CD-RW > Profile: CD-ROM > Profile: Removable Disk > Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd). > Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE > Supported modes: PACKET SAO LAYER_JUMP > Drive buf size : 1114112 = 1088 KB > Drive pbuf size: 1966080 = 1920 KB > Drive DMA Speed: 15100 kB/s 85x CD 10x DVD 3x BD > FIFO size : 4194304 = 4096 KB > Track 01: data 2858 MB > Total size: 2858 MB = 1463428 sectors > Current Secsize: 2048 > Total power on hours: 0 > Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 835068 > Starting to write CD/DVD/BD at speed 8 in real SAO mode for single session. > Last chance to quit, starting real write0 seconds. Operation starts. > Waiting for reader process to fill input buffer ... input buffer ready. > BURN-Free is ON. > Turning BURN-Free off > Starting new track at sector: 0 > Track 01:0 of 2858 MB written.cdrecord: Input/output error. write_g1: > scsi sendcmd: retryable error > CDB: 2A 00 00 00 00 00 00 00 20 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > Sense Key: 0x [], Segment 0 > Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 > Sense flags: Blk 0 (not valid) > cmd finished after 23.946s timeout 200s > > write track data: error after 0 bytes > cdrecord: A write error occured. > cdrecord: Please properly read the error message above. > Writing time: 29.002s > Average write speed 74.7x. > Fixating... > Fixating time: 22.355s > cdrecord: fifo had 64 puts and 1 gets. > cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. > > I destroyed all my spare media, so I'm also spared from burning problems > for now ;) And what kind of spare media was that? > I'm quite puzzled that only I have reported such problems, > it's like I'm on CURRENT again.. I burned bunch of DVD-R, DVD+R and DVD+R DL on FreeBSD 9.0 without any problems, using growisofs from ports. Only problem I ever had was mounting multi-sesion after 4GB (but -r flag is nice workaround). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: recent 8.2-STABLE commits break nullfs for tinderbox?
On 12/22/10, Jeremy Chadwick wrote:
> On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote:
>> Am 22.12.2010 13:44, schrieb Mike Tancsa:
>> > On 12/22/2010 7:03 AM, Matthias Andree wrote:
>> >> Greetings,
>> >>
>> >> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to
>> >> nullfs, zfs,
>> >> vfs, or thereabouts have broken Tinderbox for me.
>> >>
>> >> I'm mounting my ports tree via nullfs, which has been working fine for
>> >> a year.
>> >>
>> >> Any ideas, or further info needed?
>> >
>> > Hi,
>> >Whats specifically broken ? Two of the freebsd tinderbox machines are
>> > RELENG_8 from Dec 3 and they are fine. However, they dont use nullfs,
>> > just zfs and ufs. Is it just nullfs thats broken ? What are the errors
>> > you are getting ?
>>
>> I updated after that.
>>
>> mount_nullfs /usr/ports.cvs /usr/local/tinderbox/portstrees/FreeBSD/ports
>> fails
>> with "resource conflict avoided". I'll now rebuild GENERIC from scratch
>> (including "make clean") to see if that helps.
>>
>> Tried switching to NFS, this appears to work now.
>
> FWIW, i can't find this error message ("resource conflict avoided")
> anywhere in /usr/src, /usr/include, nor /usr/ports on RELENG_8 source
> dated from 2 hours ago.
>
> grep -ri "resource conflict" /usr/src does return some results, but
> nothing that looks identical to the string you posted.
>
> Only reason I'm pointing this out: it would be good to find the commit
> that breaks things for you, if there is such a commit, but we need
> something to key off of.
Perhaps OP means "resource deadlock avoided"?
Such message appears if you try to mount same mount point with nullfs
twice - which doesnt have sense.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Installworld deletes libc
On 9/22/08, Jason C. Wells <[EMAIL PROTECTED]> wrote: > Jason C. Wells wrote: >> Jeremy Chadwick wrote: >>> On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote: I have the problem similar to one described in 20071024 UPDATING. The build is running inside a jail. The system is 6.2-RELEASE. I supped this moring. I have the correct lib/Makefile. During installworld I receive an error: install: /lib/libc.so.6: chflags: Operation not permitted *** Error code 71 Stop in /usr/src/lib/libc. My situation is different in the libc is erased in the process. Copying the new libc.so.6 from /usr/obj does not fix the problem. Any ideas? >>> >>> Sounds like kern.securelevel is in the way. See security(7). >> >> The securelevel would normally prevent the deletion of a file. The >> secure level of this jail is -1 in any case so the schg flag should be >> ignored. security.jail.chflags_allowed=0 seems to supersede the >> securelevel according to sysctl(8). >> >> Some part of installworld is misbehaving in the jail. The security >> mechanisms in securelevel and security.jail.chflags_allowed are not >> working. > > I should add that 'systcl security.jail.chflags_allowed=1' allowed > installworld to proceed without error. That solves my immediate problem. > There appears to be a bug in the security mechanism. sysctl -d security.jail.chflags_allowed security.jail.chflags_allowed: Processes in jail can alter system file flags It is not bug in security mechanism. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-stable: a hung process - scheduler bug?
On 9/23/08, Mikhail Teterin <[EMAIL PROTECTED]> wrote: > Hello! > > I was trying to build OpenOffice using all of my 4 CPUs. To be able to > do other work on the machine comfortably, I ran the build under nice, > and assigned real-time priority to the two Xorg processes. > The build started at about 23:10 last night, and hung at 23:46. The > procstat output for the make's process group is: > > PID PPID PGID SID TSID THR LOGINWCHAN EMUL > COMM > 8371 2425 8371 2425 2425 1 mi wait FreeBSD ELF64 make > 12254 8371 8371 2425 2425 1 mi wait FreeBSD ELF64 sh > 12255 12254 8371 2425 2425 1 mi pause FreeBSD ELF64 > tcsh > 12262 12255 8371 2425 2425 1 mi wait FreeBSD ELF64 > perl5.8.8 > 33010 12262 8371 2425 2425 1 mi wait FreeBSD ELF64 > perl5.8.8 > 33011 33010 8371 2425 2425 1 mi wait FreeBSD ELF64 sh > 33012 33011 8371 2425 2425 1 mi wait FreeBSD ELF64 dmake > 37126 33012 8371 2425 2425 1 mi - FreeBSD ELF64 dmake > > The last line worries me greatly... According to "procstat -t", there is > only one thread there: > > PIDTID COMM TDNAME CPU PRI STATE > WCHAN > 37126 100724 dmake- 1 193 sleep - > > And trying to "ktrace -p 37126" returns (even to root, even in /tmp): > > ktrace: ktrace.out: Operation not permitted > > There are no problems ktrace-ing 33012, but nothing comes from there, as > that process simply waits for its child. I guess, the child -- 37126 was > (v)forked to launch a compiler or some such and remains stuck in between > (v)fork and exec somewhere... > > The OS is: FreeBSD 7.0-STABLE/amd64 from Sat Jul 26, 2008 and the box is > otherwise perfectly functional. The scheduling-related options are set > as such: > > options SCHED_4BSD # 4BSD scheduler > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B > real-time extensions > > Let me know, what else I can do to help fix this bug -- I'm going to > reboot the machine tonight... Should I switch to SCHED_ULE as a > work-around? SCHED_BSD4 is suboptimal for 4 CPUs, and it is replaced with SCHED_ULE on 7 STABLE. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpi driver freeze on boot
On 9/30/08, Henrik Hudson <[EMAIL PROTECTED]> wrote: > I've got a HP dv8000 laptop. Setting up the wpi driver for wireless freezes > the system on boot with the following error: > > wpi0 requested unsupported memory range > wpi0: could not allocate memory resource > > It lists a pcbi device (pcbi4 i think) and an actual memory range, but since > I > have to reboot using kernel.old the /var/run/dmesg.boot is wiped with the > info. Is there anyway to grab the info when it freezes when it reboots? Perhaps, entering single-user mode. Add this lines to your kernel to help debug problem. makeoptions DEBUG=-g options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpi driver freeze on boot
On 9/30/08, Henrik Hudson <[EMAIL PROTECTED]> wrote: > On Tuesday 30 September 2008, "Paul B. Mahol" <[EMAIL PROTECTED]> sent a > missive stating: >> On 9/30/08, Henrik Hudson <[EMAIL PROTECTED]> wrote: >> > I've got a HP dv8000 laptop. Setting up the wpi driver for wireless >> > freezes the system on boot with the following error: >> > >> > wpi0 requested unsupported memory range >> > wpi0: could not allocate memory resource >> > >> > It lists a pcbi device (pcbi4 i think) and an actual memory range, but >> > since I >> > have to reboot using kernel.old the /var/run/dmesg.boot is wiped with >> > the >> > info. Is there anyway to grab the info when it freezes when it reboots? >> >> Perhaps, entering single-user mode. > > Nope. Disable ACPI, safe-mode and single user don't help at all. Ah, I see it, there is no way to look dmesg output in that way because it was never actually saved. >> Add this lines to your kernel to help debug problem. >> >> makeoptions DEBUG=-g >> options KDB >> options DDB >> options GDB >> options INVARIANTS >> options INVARIANT_SUPPORT >> options WITNESS >> options WITNESS_SKIPSPIN > > This doesn't really add anything to the output near the wpi freeze and I > still This one should put you into kdb when system panics, from where you could post output of bt. > can't get to the actual message, since when I reboot it wipes it out. Any > other isolation steps or ways to get detailed info to at least a cut and > pastable state? In that case you need to enter to kdb as soon as possible during boot, and sidestep each boot instruction until something bad happens, well it is not trivial task at all. For more info you may read developers-hanbook. (Located in /usr/share/doc/en/books/) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE panics when loading USB modules x2
On 10/8/08, Bruce M Simpson <[EMAIL PROTECTED]> wrote: > Hi, > > I just had 7.0-RELEASE crash again, whilst kldloading the uplcom.ko module > in multi-user mode with X running, and no USB serial devices plugged in. > > The T43 immediately resets, I don't get a chance to drop into a debugger. > > This seems like a pretty serious USB regression. Is anyone looking into it? > Are these things a thing of the past with the "new" USB code? usb2 have uplcom2 inside usb2_serial module. try it and report outcome. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of Flash 9 on stable
On 10/14/08, Kevin Oberman <[EMAIL PROTECTED]> wrote: > I have seen some messages that imply that flashplugin9 might be usable > on STABLE. The port is sill marked IGNORE, though: > ** Port marked as IGNORE: www/linux-flashplugin9: > Unstable, no sound, generally unusable state > Maybe, but the fix is still not MFCed to STABLE, it is only available in CURRENT. > On Sat, Oct 04, 2008 at 02:08:16PM +, Konstantin Belousov wrote: > > > > kib 2008-10-04 14:08:16 UTC > > > > > > > > > > > > FreeBSD src repository > > > > > > > > > > > > Modified files: > > > > > > sys/compat/linprocfs linprocfs.c > > > > > > sys/fs/procfsprocfs_map.c > > > > > > Log: > > > > > > SVN rev 183600 on 2008-10-04 14:08:16Z by kib > > > > > > > > > > > > Change the linprocfs /maps and procfs /map handlers to use > > > > > > sbuf instead of doing uiomove. This allows for reads from non-zero > > > > > > offsets to work. > > > > > > > > > > > > Patch is forward-ported des@' one, and was adopted to current code > > > > > > by dchagin@ and me. > > > > > > > > > > > > Reviewed by:des (linprocfs part) > > > > > > PR: kern/101453 > > > > > > MFC after: 1 week > > > >
Re: LevelOne WPC-0301 11g Wireless CardBus
On 10/31/08, Oliver Fromme <[EMAIL PROTECTED]> wrote: > However, a simple "ifconfig ath0 scan" never terninates. > I have to press ^C. Is this normal? FYI, if you set card to manual roaming, that simple command will work. In other scenarios "ifconfig ath0 list scan" works. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: swap_pager: indefinite wait
On 11/17/08, Sossi Andrej <[EMAIL PROTECTED]> wrote: > Hello, > I manage a www (apache), database (postgresql) and e-mail (qmail) with > about 100 Internet domains. > We recently purchased a DELL MD3000i server with data access through > ISCSI protocol. > I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI > (v. 2.1) and SCHED_ULE scheduler. > The server's local disk configuration is: > 512 MB / > 1024 MB SWAP > 254 MB / var > 2048MB / var/ qmail > 512 MB /tmp > ~ 70 GB /usr > > The apache data (/usr/local/www), postgre (/usr/local/pgsql) and qmail > (/usr/local/vpopmail) are instead on the partition on ISCSI. After > installing all the necessary softwares I tested the machine as mail > server for a one domain and everything worked fine for 2-3 days. > I wanted to test the correct functioning of qmail and of the > reading/writing on ISCSI. On the end of testing I decided to transfer > all of data (www, DB and e-mail) on the FreeBSD 7.0. I compressed all > the data on the original server (on tar.gz format). I transferred them > on the new server and started to decompress the files. Www data have > been decompressed correctly on the ISCSI disk. But while the messages > were being decompressed (~80GB of tar.gz) and all the DB were being > restored, the server crashed. Which application were used for decompression? > The error shown was: > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096 I believe this can happen any time when to much of swap partition is used. If this sort of thing happens often, review memory management of application(s) that is causing such scenario, if that is application fault - you have two choices: get more RAM (this may not always help) or use another application. Increasing swap partition will not help much > This message repeated every 30 seconds. > While restarting with the single user mode I checked there wasn't any > message after the crash in /var/log/messages. > > I think 1GB of swap should be enough, since with this configuration on > FreeBSD 5.5 everything worked for over 270 days without reboot. > The local disks are 2 of ~80GB in RAID 1 (mirror) with Gmirror > before installing FreeBSD I tested the 2 disks with the badblocks > software on Slackware which didn't find any r/w error. > > Can somebody help me understand why the system crashed this way or how > to avoid future crash? > It's a production server and I can't afford an out-of-service or data loss. > > Thank you very much and kind regards. > > -- > Sossi Andrej > - > DotCom Information technology > > Via Biancospino, 9 > 34151 - Opicina (TS) > Italy > > tel: +39 040 2158191 > fax: +39 040 0641954 > E-mail: [EMAIL PROTECTED] > > > Ai sensi del D.lgs n. 196 del 30.06.03 (Codice Privacy) si precisa che > le informazioni contenute in questo messaggio sono riservate e ad uso > esclusivo del destinatario. Qualora il messaggio in parola Le fosse > pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non > inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie > > This message, for the D.lgs n. 196 / 30.06.03 (Privacy Code), may > contain confidential and/or privileged information. If you are not the > addressee or authorized to receive this for the addressee, you must not > use, copy, disclose or take any action based on this message or any > information herein. If you have received this message in error, please > advise the sender immediately by reply e-mail and delete this message. > Thank you for your cooperation. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MFC ZFS: when?
On 11/22/08, Zaphod Beeblebrox <[EMAIL PROTECTED]> wrote: > In several of the recent ZFS posts, multiple people have asked when this > will be MFC'd to 7.x. This query has been studiously ignored as other > chatter about whatever ZFS issue is discussed. > > So in a post with no other bug report or discussion content to distract us, > when is it intended that ZFS be MFC'd to 7.x? Once no new bugs appear any more, and old one are fixed. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ext2fuse: user-space ext2 implementation
On 12/8/08, Bruce M. Simpson <[EMAIL PROTECTED]> wrote: > I have rolled a port for ext2fuse: > http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar Ignoring fact that is buggy, slooow and port doesnt have any cache implemented and port leaves files behind in share/doc/ext2fuse when package deleted it looks fine. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1RC1: system hang
On 12/12/08, Guy Helmer wrote: > I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout > as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped > into the kernel debugger on the VGA console and transcribed the > following information (if I omit anything critical, let me know -- the > machine is still sitting at the debugger prompt) : > > > where > pid 20 tid 100018 td 0xc45008c0 > kdb_enter_why > scgetc > sckdbevent > kdbmux_intr > kdbmux_kdb_intr > taskqueue_run > taskqueue_swi_giant_run > ithread_loop > fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 > fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 > > > show allpcpu > cpuid 0 in idle > cpuid 1: proc 23457 > cpuid 2: idle > cpuid 3: swi6 proc 20 what is proc 23457? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1RC1: system hang
On 12/12/08, Guy Helmer wrote: > Paul B. Mahol wrote: >> On 12/12/08, Guy Helmer wrote: >> >>> I have a recurring hang on FreeBSD 7.1 roughly-RC1 (releng_7_1 checkout >>> as of 2008-12-08) on a dual-CPU hyperthreaded Xeon i386. I've dropped >>> into the kernel debugger on the VGA console and transcribed the >>> following information (if I omit anything critical, let me know -- the >>> machine is still sitting at the debugger prompt) : >>> >>> > where >>> pid 20 tid 100018 td 0xc45008c0 >>> kdb_enter_why >>> scgetc >>> sckdbevent >>> kdbmux_intr >>> kdbmux_kdb_intr >>> taskqueue_run >>> taskqueue_swi_giant_run >>> ithread_loop >>> fork_exit(c063cce0, c44ac590, e4a36d38) at 0xc063a624 = fork_exit+0x94 >>> fork_trampoline() at 0xc07e41a0 = fork_trampoline+0x8 >>> >>> > show allpcpu >>> cpuid 0 in idle >>> cpuid 1: proc 23457 >>> cpuid 2: idle >>> cpuid 3: swi6 proc 20 >>> >> >> >> what is proc 23457? >> > proc 23457 is "filter", an Autonomy KeyView Filter API program (extracts > text out of various document formats) that is being run using FreeBSD 6 > compatibility libraries. > > Guy > > Could you give most interesting part of "ps" output. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ext2fuse: user-space ext2 implementation
On 12/13/08, Bruce Simpson wrote: > Paul B. Mahol wrote: >> On 12/8/08, Bruce M. Simpson wrote: >> >>> I have rolled a port for ext2fuse: >>> http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar >>> >> >> Ignoring fact that is buggy, slooow and port doesnt have any cache >> implemented >> and port leaves files behind in share/doc/ext2fuse when package >> deleted it looks fine. >> > > Can you please relay this feedback to the authors of ext2fuse? > > As mentioned earlier in the thread, the ext2fuse code could benefit from > UBLIO-ization. Are you or any other volunteers happy to help out here? Well, first higher priority would be to fix existing bugs. It would be very little gain with user cache, because it is already too much IMHO slow and adding user cache will not make it faster, but that is not port problem. > Can you elaborate further on the files being left behind by the port? I > didn't see this issue in my own testing. It install files in this way: test -z "/usr/local/share/doc/ext2fuse" || ./install-sh -c -d "/usr/local/share/doc/ext2fuse" make deinstall and pkg_delete doesnt not remove that files/dir, -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ext2fuse: user-space ext2 implementation
On 12/14/08, Bruce M Simpson wrote: > Paul B. Mahol wrote: >>> Can you please relay this feedback to the authors of ext2fuse? >>> >>> As mentioned earlier in the thread, the ext2fuse code could benefit from >>> UBLIO-ization. Are you or any other volunteers happy to help out here? >>> >> >> Well, first higher priority would be to fix existing bugs. It would be >> very little >> gain with user cache, because it is already too much IMHO slow and >> adding user cache >> will not make it faster, but that is not port problem. >> > > I'm not aware of bugs with ext2fuse itself; my work on the port was > merely to try to raise awareness that a user-space project for ext2 > filesystem access existed. > > Can you elaborate further on your experience with ext2fuse which seems > to you to be buggy, i.e. symptoms, root cause analysis etc. ? Have you > reported these to the author(s)? I have read TODO. > Have you measured the performance? Is the performance sufficient for the > needs of an occasional desktop user? Performance was not sufficient, and adding user cache will not improve access speed on first read. After mounting ext2fs volume (via md(4)) created with e2fsprogs port and copying data from ufs to ext2, reading was quite slow. Also ext2fuse after mount doesnt exits it is still running displaying debug data - explaining why project itselfs is in alpha state. > I realise we are largely involved in content-free argument here, however > the trade-off of ext2fuse vs ext2fs in the FreeBSD kernel source tree, > is that of a hopefully more actively maintained implementation vs one > which is not maintained at all, and any alternatives for FreeBSD users > would be welcome. Project itself doesnt look very active, but I may be wrong. It is in alpha state as reported on SF. IMHO it is better to maintain our own because it is in better shape, but I'm not intersted in ext* as developer. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Very serious cooling issues CURRENT/STABLE
On 12/21/08, Nathan Lay wrote: > acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 37.0C > hw.acpi.thermal.tz0.active: -1 Is this one ever changed? > hw.acpi.thermal.tz0.passive_cooling: 1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 89.5C > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 93.0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 This one means that coling will never be used, why: my output looks like this: hw.acpi.thermal.tz0._ACx: 85.0C 75.0C 60.0C 50.0C -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: 5 > hw.acpi.thermal.tz0._TC2: 4 > hw.acpi.thermal.tz0._TSP: 600 You can play with all thermal values once you enable: hw.acpi.thermal.user_override But acpi may redo such values again after some time. You only real workaround is to use modified acpi ASL: it is explained in handbook. In my case I fixed in that way bogus kernel message "_CRT value is absurd, ignored". -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Very serious cooling issues CURRENT/STABLE
On 12/21/08, Nathan Lay wrote: > Paul B. Mahol wrote: >> On 12/21/08, Nathan Lay wrote: >> >>> acpi.thermal.min_runtime: 0 >>> hw.acpi.thermal.polling_rate: 10 >>> hw.acpi.thermal.user_override: 0 >>> hw.acpi.thermal.tz0.temperature: 37.0C >>> hw.acpi.thermal.tz0.active: -1 >>> >> Is this one ever changed? >> >> >>> hw.acpi.thermal.tz0.passive_cooling: 1 >>> hw.acpi.thermal.tz0.thermal_flags: 0 >>> hw.acpi.thermal.tz0._PSV: 89.5C >>> hw.acpi.thermal.tz0._HOT: -1 >>> hw.acpi.thermal.tz0._CRT: 93.0C >>> hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 >>> >> >> This one means that coling will never be used, why: >> my output looks like this: >> hw.acpi.thermal.tz0._ACx: 85.0C 75.0C 60.0C 50.0C -1 -1 -1 -1 -1 -1 >> >> >>> hw.acpi.thermal.tz0._TC1: 5 >>> hw.acpi.thermal.tz0._TC2: 4 >>> hw.acpi.thermal.tz0._TSP: 600 >>> >> >> You can play with all thermal values once you enable: >> hw.acpi.thermal.user_override >> >> But acpi may redo such values again after some time. >> You only real workaround is to use modified acpi ASL: >> it is explained in handbook. >> >> In my case I fixed in that way bogus kernel >> message "_CRT value is absurd, ignored". >> >> >> > hw.acpi never displayed thermal values for some reason. However, after > loading acpi_ibm, I can query those values without a problem > dev.acpi_ibm.0.thermal: 49 41 33 48 27 -1 22 -1 > > I'm not sure the critical temperature (99C) is a problem, but what I > have observed is you should never be near it. None of these thinkpads > got over 80C under load with FreeBSD installed until recently. ACPI's > ASL does not appear to be the problem as it has worked correctly in the > past. Until recenty when, can you point into svn revision? If the same overheat happens with acpi disabled that I dont see how freebsd acpi can help you. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bwi: no DS tssi no OFDM tssi
On 1/12/09, Neal Hogan wrote: > Hello, > >I am attempting to get by broadcom wifi card up and running, am sick of > trying to get ndis working, and am attempting to use the bwi driver > (originating in dragonflyBSD). I'm hoping others here have tried to do the > same and have some pointers. I'm using 7.1-RELEASE (system/source are > in-sync) and my card is a BCM94306MP. My dmesg is posted below. > > Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in my > /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP request > to my WEP encrypted access point. Yet, it doesn't get an offer and says that > *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen > references to DS/OFDM tssi, I'm not sure what info to provide. My research > is not leading anywhere helpful. Thanks. > > > > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 > n...@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > Features=0x383f9ff > AMD Features=0xc0480800 > real memory = 468647936 (446 MB) > avail memory = 444530688 (423 MB) > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > acpi_ec0: port 0x62,0x66 on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid > pci0: on pcib0 > agp0: on hostb0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x9000-0x90ff mem > 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on > pci1 > ohci0: mem > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 4 ports with 4 removable, self powered > pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff > irq 5 at device 6.0 on pci0 > pcm0: > pcm0: [GIANT-LOCKED] > pcm0: [ITHREAD] > isab0: at device 7.0 on pci0 > isa0: on isab0 > pci0: at device 8.0 (no driver attached) > bwi0: mem > 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 > bwi0: [ITHREAD] > bwi0: regwin: chipcommon (0x800), rev 2, vendor 0x4243 > bwi0: BBP: id 0x4306, rev 0x2, pkg 0 > bwi0: nregwin 6, cap 0x002a > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > bwi0: has TX stats > bwi0: MAC: rev 4 > bwi0: regwin: pcmcia (0x80d), rev 1, vendor 0x4243 > bwi0: regwin: v90 codec (0x807), rev 1, vendor 0x4243 > bwi0: regwin: pci (0x804), rev 7, vendor 0x4243 > bwi0: regwin: 802.11 MAC (0x812), rev 4, vendor 0x4243 > bwi0: ignore second MAC > bwi0: bus rev 0 > bwi0: pci is enabled > bwi0: card flags 0x000f > bwi0: 0th led, act 3, lowact 0 > bwi0: 1th led, act 5, lowact 0 > bwi0: 2th led, act 4, lowact 0 > bwi0: 3th led, act 0, lowact 0 > bwi0: 802.11 MAC was already disabled > bwi0: PHY is linked > bwi0: PHY: type 2, rev 1, ver 1 > bwi0: PHY: 802.11G attach > bwi0: RF: manu 0x17f, type 0x2050, rev 2 > bwi0: bus rev 0 > bwi0: PHY is linked > bwi0: 30bit bus space > bwi0: max txpower from sprom: 57 dBm > bwi0: invalid antenna gain in sprom > bwi0: ant gain 8 dBm > bwi0: region/domain max txpower 76 dBm > bwi0: max txpower 57 dBm > bwi0: sprom idle tssi: 0x003e > bwi0: TSSI-TX power map: > 71 71 70 70 70 70 70 69 > 69 69 69 69 68 68 68 67 > 67 67 66 66 66 66 65 65 > 65 64 64 64 63 63 63 62 > 61 61 61 60 59 59 58 57 > 57 55 55 54 53 52 51 50 > 49 48 47 44 43 42 39 37 > 35 32 29 26 22 18 14 8 > bwi0: idle tssi0: 62 > bwi0: bus rev 0 > bwi0: locale: 6 > bwi0: WARNING: using obsoleted if_watchdog interface > bwi0: Ethernet address: 00:90:4b:61:02:45 > cbb0: irq 11 at device 10.0 on pci0 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [ITHREAD] > fwohci0: mem > 0xd0009000-0xd00097ff,0xd000-0xd0003fff irq 10 at device 12.0 on > pci0 > fwohci0: [FILTER] > fwohci0: OHCI version 1.10 (ROM=1) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a > fwohci0: Phy 1394a available S400, 1 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a > fwe0: Ethernet address: 02:0d:9d:43:0c:6a > fwip0: on firewire0 > fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe, > S400, maxrec 2048 > sbp0: on firewire0 > dcons_crom0: on firewire0 > dcons_crom0:
Re: bwi: no DS tssi no OFDM tssi
On Mon, Jan 12, 2009 at 8:08 PM, Neal Hogan wrote: > I installed the firmware stuff from the dragonfly bwi(4) man page, yet I > have the same issue. Is there a way to tell whether the firmware they > provide supports my card? Like I said, I can locate my access point (and > others that are around) and ask for an IP . . . it seems as though I'm so > close. I'm fairly certain that I have all of the avliable bwi(4) bits > installed correctly. > > I dwonloaded and installed the driver and added *if_bwi_load="YES"* in my > loader.conf. I loaded the .ko file (bwi_v3). I downloaded and installed the > firmware from dflyBSD and followed their directions. Yet I get no offer. Is > the fact that I fail to get an offer indicate the firmware incompatinbility? 9 in BCM94306MP indicates that its supports 80211n and as such certainly it is not supported with bwi(4) and reason is that bwi developers do not plan to add support for 4 version firmware (when last time I played with bwi). > Anyway, thanks for you help. > > On Mon, Jan 12, 2009 at 12:32 PM, Paul B. Mahol wrote: >> >> On 1/12/09, Neal Hogan wrote: >> > Hello, >> > >> >I am attempting to get by broadcom wifi card up and running, am sick >> > of >> > trying to get ndis working, and am attempting to use the bwi driver >> > (originating in dragonflyBSD). I'm hoping others here have tried to do >> > the >> > same and have some pointers. I'm using 7.1-RELEASE (system/source are >> > in-sync) and my card is a BCM94306MP. My dmesg is posted below. >> > >> > Bwi(4) is installed and it recognizes my card (*if_bwi_load-"YES"* is in >> > my >> > /etc/rc.conf and *bwi_v3* and *if_bwi* are loaded). I can send a IP >> > request >> > to my WEP encrypted access point. Yet, it doesn't get an offer and says >> > that >> > *no DS tssi* and *no OFDM tssi* Being new to bwi(4) and have never seen >> > references to DS/OFDM tssi, I'm not sure what info to provide. My >> > research >> > is not leading anywhere helpful. Thanks. >> > >> > >> > >> > >> > Copyright (c) 1992-2009 The FreeBSD Project. >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> > The Regents of the University of California. All rights reserved. >> > FreeBSD is a registered trademark of The FreeBSD Foundation. >> > FreeBSD 7.1-RELEASE #0: Sat Jan 10 19:07:15 CST 2009 >> > n...@frege.lambdaserver:/usr/obj/usr/src/sys/GENERIC >> > Timecounter "i8254" frequency 1193182 Hz quality 0 >> > CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) >> > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 >> > >> > >> > Features=0x383f9ff >> > AMD Features=0xc0480800 >> > real memory = 468647936 (446 MB) >> > avail memory = 444530688 (423 MB) >> > kbd1 at kbdmux0 >> > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, >> > RF5413) >> > acpi0: on motherboard >> > acpi0: [ITHREAD] >> > acpi0: Power Button (fixed) >> > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 >> > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 >> > acpi_ec0: port 0x62,0x66 on acpi0 >> > pcib0: port 0xcf8-0xcff on acpi0 >> > pci_link5: BIOS IRQ 10 for 0.10.INTA is invalid >> > pci0: on pcib0 >> > agp0: on hostb0 >> > pcib1: at device 1.0 on pci0 >> > pci1: on pcib1 >> > vgapci0: port 0x9000-0x90ff mem >> > 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on >> > pci1 >> > ohci0: mem >> > 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 >> > ohci0: [GIANT-LOCKED] >> > ohci0: [ITHREAD] >> > usb0: OHCI version 1.0, legacy support >> > usb0: SMM does not respond, resetting >> > usb0: on ohci0 >> > usb0: USB revision 1.0 >> > uhub0: on >> > usb0 >> > uhub0: 4 ports with 4 removable, self powered >> > pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff >> > irq 5 at device 6.0 on pci0 >> > pcm0: >> > pcm0: [GIANT-LOCKED] >> > pcm0: [ITHREAD] >> > isab0: at device 7.0 on pci0 >> > isa0: on isab0 >> > pci0: at device 8.0 (no driver attached) >> > bwi0: mem >> > 0xd0004000-0xd0005fff irq 9 at device 9.0 on pci0 >> > bwi0: [ITHREAD] >> > bwi0: regwin: chipcommon (0x800), rev 2, vendor
Re: kernel panics when connected through wpi to apple extreme ap
On 1/15/09, Marc Peters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > hello list, > > i have a lenovo t60 with an integrated intel 3945ABG wireless chipset. > when i was running 7.1-PRERELEASE i realised that the network connection > of my wpi died after some time when connected to the mention apple > access point. i had to restart the card and everything went fine, for > some time (about half an hour). since 7.1-RELEASE and now with > 7.1-STABLE the kernel panics with a fatal trap and dumps it's core after > some minutes (this output ist from -RELEASE-p1, but it's identical to > the one i got from -STABLE): > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x > fault code= supervisor read, page not present > instruction pointer = 0x20:0xc0deadfc > stack pointer = 0x28:0xe58bbbe0 > frame pointer = 0x28:0xe58bbc9c > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 25 (wpi0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 6m 14s > Physical memory: 2034 MB > Dumping 149 MB: 134 118 192 86 70 65 38 22 6 > Dump complete > Automatic reboot in 15 seconds - press a key on the console to abort > > when i run this box connected to a netgear-ap i have at home, everything > is fine (and was before, no panics, no connection dropping). i have the > dump at hand, but since it's 150 MB i won't send it around via mail. if > anyone is interested, i can upload it somewhere and send the link. > > anyone any ideas? Enable textdump(8) and post bt output from debuger once panic happen. (I'm not going to download 150MB) > marc > > dmesg: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.1-STABLE #0: Wed Jan 14 13:23:00 CET 2009 > r...@lappi.agentur.local:/usr/obj/usr/src/sys/GENERIC_DRM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x2010 > AMD Features2=0x1 > Cores per package: 2 > real memory = 2146238464 (2046 MB) > avail memory = 2090221568 (1993 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address > or length:0102C/0 [20070320] > ioapic0: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, 7ff0 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_hpet0: iomem 0xfed0-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x2000-0x20ff mem > 0xd800-0xdfff,0xee10-0xee10 irq 16 at device 0.0 on pci1 > drm0: on vgapci0 > vgapci0: child drm0 requested pci_enable_busmaster > info: [drm] Initialized radeon 1.29.0 20080613 > hdac0: mem > 0xee40-0xee403fff irq 17 at device 27.0 on pci0 > hdac0: HDA Driver Revision: 20090110_0123 > hdac0: [ITHREAD] > pcib2: irq 20 at device 28.0 on pci0 > pci2: on pcib2 > em0: port 0x3000-0x301f mem > 0xee00-0xee01 irq 16 at device 0.0 on pci2 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: 00:16:41:e3:4a:ff > pcib3: irq 21 at device 28.1 on pci0 > pci3: on pcib3 > wpi0: mem 0xedf0-0xedf00fff irq 17 > at device 0.0 on pci3 > wpi0: Ethernet address: 00:19:d2:07:cf:36 > wpi0: [ITHREAD] > pcib4: irq 22 at device 28.2 on pci0 > pci4: on pcib4 > pcib5: irq 23 at device 28.3 on pci0 > pci12: on pcib5 > uhci0: port 0x1800-0x181f irq 16 at > device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x1820-0x183f irq 17 at > device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x1840-0x185f irq 18 at > device 29.2 on pci
Re: atheros problem
On 12/8/09, Pete Carah wrote: > With a recent build of 8-stable (last week and again yesterday) the ath > 9280 driver doesn't work; wpa_supplicant says "scanning" forever, and if > one observes ifconfig it is scanning some of the 11a frequencies and no > 11g ones. It also doesn't pick up a legit 11a AP at home, nor does it see > *any* AP at work (there are about 12 visible from where I sit). The > card works in both fedora and windoze (though fedora has a very > annoying 7 second pause every minute or so (irregular intervals). > > I can stop wpa_supplicant and manually up it and give ifconfig scan; > this hangs forever and also only appears to be listing 11a freqs when you > look with ifconfig from another window. > > It had worked before... The only change that shows up in the ath driver > is "Add WorldB SKU" to ah_regdomain.c on the 25th. My previous > build was somewhere around the 17th so that must have broken it. A > cursory svn diff doesn't look bad to me but I only looked at the syntax. > And none of the net80211 files have changed since the 7th in my source tree. > > A second problem that also crept up in the most recent update Please separate problems (do not post about separate issues in same message). > (yesterday) one of 3 instances of acpi_ec0 causes a panic. If I specify > boot_verbose="YES" the panic goes away!! Since this is a laptop with no > serial port (any modern laptop :-( I can't capture the panic > directly, only copy it with a camera (aren't digital cameras > wonderful). Looking at the last message printed in verbose, I'm guessing an > access to a freed area; why verbose "fix"es it I don't know (maybe > printing reallocates?) > > This laptop has always given a string of error messages regarding its > ec0. (Acer 4730; dual-core 2gig intel cpu, intel chipset, running as amd64) > (I run 32-bit windoze but 64 bsd and linux.) Try # ifconfig wlan0 list scan and there is wlandebug(8) and athdebug (in tools if you have source) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ndis(4) on amd64
Hi, I'm looking for users of NDISulator on amd64. Have anyone managed to get working ndis(4) on amd64? -- Paul B Mahol ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Broadcom USB wireless support?
On 2/16/10, Jeff Dowsley wrote: > Gentles > > I have an old HP Pavillion DV6000 laptop, which has a Broadcom USB > wireless device. Worked under Windows Vista. I installed freeBSD 8- > stable, and see as the last line in dmesg > > ugen2.2: at usbus2 > > Ferreting with google suggests that 8.0 might have usb support for > the ndis wrapper, but I am unable to get any joy either using the HP > bcmwl5 drivers for the DV6000, or in attempting to use the bwi driver. > > (I have an old Compaq N1020 with a LinkSys wireless PCMCIA card, > which I have successfully generated the ndis wrapper and works > happily under 8-stable) > > Any thoughts? Firts, make sure you are using right driver. Second make sure that driver is for XP, because NDISulator supports only 5.1 NDIS api. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freeze on closing terminal that runs wpa_supplicant
On 3/17/10, Mathias Sogorski wrote: > Hello! > I am running 8.0-RELEASE on a notebook with the Intel 3945 WiFi. I usually > start wpa_supplicant [...]& on a terminal when entering gnome followed by > the dhcpcd call to use the WiFi connection. After having finished work and > closing the terminal that runs wpa_supplicant, everything freezes and I have > to turn the power off. Any suggestions? That should not happen. So report the bug. You managed to get backtrace? Did kernel actually crashed? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ath0: kernel panic when adhoc mode.
On 4/14/10, Lystopad Olexandr wrote: > Hi! > > I install 8.0 FreeBSD, upgrade it to yesturday stable. > I need to create wireless link in adhoc mode. > Help me to do this. > > > I put a wireless card into this box: > > a...@pci0:3:3:0:class=0x02 card=0xcc2114b9 chip=0x0013168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = '802.11a/b/g Wireless Adapter (AR5212)' > class = network > subclass = ethernet > cap 01[44] = powerspec 2 supports D0 D3 current D0 > > > > when I do: > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > server reboot with kernel panic: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0791612 > stack pointer = 0x28:0xd2f42ba4 > frame pointer = 0x28:0xd2f42bac > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 0 (ath0 taskq) > trap number = 12 > panic: page fault > cpuid = 1 > Uptime: 3m35s > Physical memory: 439 MB > Dumping 80 MB: 65 49 33panic: bufwrite: buffer is not busy??? > cpuid = 1 > 17 1 > > #0 doadump () at pcpu.h:246 > 246 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump () at pcpu.h:246 > #1 0xc06b3497 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 > #2 0xc06b3789 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:579 > #3 0xc08b63bc in trap_fatal (frame=0xd2f42b64, eva=65535) > at /usr/src/sys/i386/i386/trap.c:938 > #4 0xc08b6620 in trap_pfault (frame=0xd2f42b64, usermode=0, eva=65535) > at /usr/src/sys/i386/i386/trap.c:851 > #5 0xc08b6f39 in trap (frame=0xd2f42b64) at > /usr/src/sys/i386/i386/trap.c:533 > #6 0xc0899b3b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 > #7 0xc0791612 in ieee80211_getcapinfo (vap=0xc2d5f000, chan=0x) > at /usr/src/sys/net80211/ieee80211_output.c:1836 > #8 0xc0793d17 in ieee80211_beacon_construct (m=0xc2edca00, > frm=0xc2f0516e "", bo=0xc2d5f884, ni=0xc2ceb000) > at /usr/src/sys/net80211/ieee80211_output.c:2559 > #9 0xc07946db in ieee80211_beacon_alloc (ni=0xc2ceb000, bo=0xc2d5f884) > at /usr/src/sys/net80211/ieee80211_output.c:2756 > #10 0xc050eaea in ath_newstate (vap=0xc2d5f000, nstate=IEEE80211_S_RUN, > arg=-1) at /usr/src/sys/dev/ath/if_ath.c:2641 > #11 0xc0798db1 in ieee80211_newstate_cb (xvap=0xc2d5f000, npending=3) > at /usr/src/sys/net80211/ieee80211_proto.c:1654 > #12 0xc06ebf92 in taskqueue_run (queue=0xc2a84c80) > at /usr/src/sys/kern/subr_taskqueue.c:239 > #13 0xc06ec19d in taskqueue_thread_loop (arg=0xc2ada074) > at /usr/src/sys/kern/subr_taskqueue.c:360 > #14 0xc068a331 in fork_exit (callout=0xc06ec0e0 , > arg=0xc2ada074, frame=0xd2f42d38) at /usr/src/sys/kern/kern_fork.c:843 > #15 0xc0899bb0 in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:270 > (kgdb) > This is bug, please report it ASAP. > > > > dmesg is: > > 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 8.0-STABLE #0: Wed Apr 14 07:45:45 MSD 2010 > r...@serv01:/usr/obj/usr/src/sys/serv01 i386 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2194.76-MHz 686-class > CPU) > Origin = "AuthenticAMD" Id = 0x40fb2 Family = f Model = 4b Stepping = > 2 > > Features=0x178bfbff > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x1f > real memory = 536870912 (512 MB) > avail memory = 449187840 (428 MB) > ACPI APIC Table: <050407 APIC1334> > 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 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: <050407 RSDT1334> on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of fee0, 1000 (3) failed > acpi0: reservation of ffb8, 8 (3) failed > acpi0: reservation of fff8, 8 (3) failed > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, 1bf0 (3) failed > ACPI HPET table warning: Sequence is non-zero (2) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_hpet0: iomem 0xfed0-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > v
Re: devfs ignores pass0 entry at boot time
What's output of etc/devfs.conf ? On 3/10/08, Mark Nowiasz <[EMAIL PROTECTED]> wrote: > Am Sonntag, 9. März 2008 16:11:39 schrieb Denise H. G.: > > > try to write like this: > > > > add path `pass*` mode 660 > > Nope, won't do: > > tower# ls -la /dev/pass0 > crw--- 1 root operator0, 107 Mar 10 12:35 /dev/pass0 > > > there is no problem with my 7-STABLE/amd64. > > Well, all the other entries in devfs.rules are correctly applied, for > example: > > add path 'cd*' mode 660 group wheel user mark > > tower# ls -la /dev/cd* > crw-rw 1 mark wheel0, 109 Mar 10 12:35 /dev/cd0 > crw-rw 1 mark wheel0, 110 Mar 10 12:35 /dev/cd1 > > I'ts just that /dev/pass0 is being ignored at startup time... > > Regards, > Mark > -- > If *I* had a hammer, there'd be no more folk singers. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: devfs ignores pass0 entry at boot time
I could not reproduce it on i386. I moved pass entry in devfs.rules on last line and commented pass entry in devfs.conf and rebooted. Could you place pass0/* entry in nonlast line of devfs.rules and find any difference. On 3/10/08, Mark Nowiasz <[EMAIL PROTECTED]> wrote: > Am Montag, 10. März 2008 14:59:17 schrieb Paul B. Mahol: > > What's output of etc/devfs.conf ? > > own speaker root:wheel > permspeaker 0660 > perm/dev/cuaa1 0666 > > own cd0 mark:wheel > permcd0 0666 > > own cd1 mark:wheel > permcd1 0666 > permxpt00666 > > own pass0 mark:wheel > permpass0 0666 > > own pass1 mark:wheel > permpass1 0666 > > own da0 mark:wheel > permda0 0660 > permdevstat 0444 > > devfs.rules will be applied during boot time (please not the different > permission: for example cd0/1: 0666 in devfs.conf, 0600 in devfs.rules, > cd0/1 > have got 0600 permissions), just the last entry (add path 'pass*' mode 660 > group wheel user mark) will be ignored - but only at boot time, when > restarting devfs, pass0/1 will have the correct permissions/ownership. > > Regards, > Mark > -- > If *I* had a hammer, there'd be no more folk singers. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
On 2/24/09, SDH Support wrote: > >> I tried using my ath based D-Link DWL G650, which still seems to have >> some issues in regard to interrupt handling: > > > I've been able to get /most/ wireless cards working with ndiswrapper. *BSD doesnt have ndiswrapper. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: qemu+aio vs C2
On 2/26/09, Andriy Gapon wrote: > > I see something unusual and surprising for me: if I kldload aio for qemu's > sake > and then actually start qemu, I see that share of C2 in cx_usage is > constantly > dropping and then finally there is "too many short sleeps, backing off to > C1". > > This is on i386 with stable/7 as of r188116. > > I am out of ideas. And qemu guest is? Perhaps you should try changing guest kern.hz sysctl setting. I dont think related comitt got MFC-ed to STABLE. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: powerd causing crash on Mini-ITX EN1200
On 2/26/09, Ross Penner wrote: > Hi, > > When I enable powerd, it is only but a matter of time before my > machine will lock up completely. I've had this problem since I've > migrated to FreeBSD 7 from 6. FreeBSD 6 never seemed to have any > problems. I doesn't seem to create a dump so I've had no luck on that > end. I'm quite perplexed on how to proceed to help get this problem > documented so it can be fixed. > > #uname -a > FreeBSD rosbox.dyndns.org 7.1-STABLE FreeBSD 7.1-STABLE #0: Thu Feb 26 > 00:38:44 PST 2009 > r...@rosbox.dyndns.org:/usr/obj/usr/src/sys/MYKERNEL7 i386 > > Is there anything else I con provide that would be of assistance? I'm aware of livelock between syscons and powerd which is not trivial to reproduce (at least for me). Does it locks in Xorg too? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: powerd causing crash on Mini-ITX EN1200
On 2/27/09, Ross Penner wrote: > Perhaps, but I rarely run Xorg. I use the machine as a gateway for our > network in the house. I've noticed it most often when under a network > load but that might not be a real correlation. > > On Thu, Feb 26, 2009 at 2:47 PM, Paul B. Mahol wrote: >> On 2/26/09, Ross Penner wrote: >>> Hi, >>> >>> When I enable powerd, it is only but a matter of time before my >>> machine will lock up completely. I've had this problem since I've >>> migrated to FreeBSD 7 from 6. FreeBSD 6 never seemed to have any >>> problems. I doesn't seem to create a dump so I've had no luck on that >>> end. I'm quite perplexed on how to proceed to help get this problem >>> documented so it can be fixed. >>> >>> #uname -a >>> FreeBSD rosbox.dyndns.org 7.1-STABLE FreeBSD 7.1-STABLE #0: Thu Feb 26 >>> 00:38:44 PST 2009 >>> r...@rosbox.dyndns.org:/usr/obj/usr/src/sys/MYKERNEL7 i386 >>> >>> Is there anything else I con provide that would be of assistance? >> >> I'm aware of livelock between syscons and powerd which is not trivial to >> reproduce (at least for me). The locks happens for me only if kernel prints something on console while something other is being printed on vtys. So it looks like your problem is not related to syscons bugs. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: powerd causing crash on Mini-ITX EN1200
On 2/27/09, Ross Penner wrote: > On Fri, Feb 27, 2009 at 3:46 AM, Paul B. Mahol wrote: >> On 2/27/09, Ross Penner wrote: >>> Perhaps, but I rarely run Xorg. I use the machine as a gateway for our >>> network in the house. I've noticed it most often when under a network >>> load but that might not be a real correlation. >>> >>> On Thu, Feb 26, 2009 at 2:47 PM, Paul B. Mahol wrote: >>>> On 2/26/09, Ross Penner wrote: >>>>> Hi, >>>>> >>>>> When I enable powerd, it is only but a matter of time before my >>>>> machine will lock up completely. I've had this problem since I've >>>>> migrated to FreeBSD 7 from 6. FreeBSD 6 never seemed to have any >>>>> problems. I doesn't seem to create a dump so I've had no luck on that >>>>> end. I'm quite perplexed on how to proceed to help get this problem >>>>> documented so it can be fixed. >>>>> >>>>> #uname -a >>>>> FreeBSD rosbox.dyndns.org 7.1-STABLE FreeBSD 7.1-STABLE #0: Thu Feb 26 >>>>> 00:38:44 PST 2009 >>>>> r...@rosbox.dyndns.org:/usr/obj/usr/src/sys/MYKERNEL7 i386 >>>>> >>>>> Is there anything else I con provide that would be of assistance? >>>> >>>> I'm aware of livelock between syscons and powerd which is not trivial >>>> to >>>> reproduce (at least for me). >> >> The locks happens for me only if kernel prints something on console while >> something other is being printed on vtys. >> So it looks like your problem is not related to syscons bugs. >> >> -- >> Paul > > Well, it might not actually be that far off. When I have powerd > enabled, I frequently get a message on the console about 'vge watchdog > timeout' I got that similar one when using "powerd -b min" and transferring big file with ndis vap configured in adhoc mode. Probably I was just lucky that I used min instead of (h)adp. > Does anybody have any ideas on how to try and fix this issue? One nasty fix would be disabling kernel messages on console. I never tested if it actually works, or perhaps I did but forgot about it ;) : echo "kern.consmute=1" >> /boot/sysctl.conf Another, better one would be to make syscons giant free, perhaps rewriting it from scratch -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [7-STABLE] ndis interacts badly with powerd
On 3/3/09, Patrick Lamaiziere wrote: > Le Sun, 1 Mar 2009 13:00:18 +0100, > Patrick Lamaiziere : > >> [7-STABLE/i386-SMP] >> >> When I enable powerd, ndis takes all the CPU. Powerd alone and ndis >> alone works fine. >> >> The kernel threads "Windows DCP0" and "ndis0 taskq" run at >> 100%. But the machine is still running (but is very very slow), I can >> kldunload my ndis module and all is ok. >> >> I tried with a kernel (GENERIC) without SMP but there is the same >> problem. >> >> Any idea? Thanks. > > The problem was simply that the frequency was lowered too many. I have > to limit the frequency with debug.cpufreq.lowest. How much small it was? powerd -b min with 125 freq works fine on CURRENT with ndis for me (except that in such case watchdog errors are displayed on console if connection is heavily used) Note that ndis watchdog stuff have been rewritten on CURRENT. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/25/09, John wrote: > Hi list > > I configured the malo device as per the manpage. Now I'm getting panic > after the device is probed as per > http://www.growveg.org/desktop/DSC_6973-3008.jpg > > Is there a parameter I can pass to boot that will ignore this > driver/module? I have tried disable-module to no avail. Is the only > option to use the rescue disk? I need loader.conf to be ignored now in > order to get the system up at all. Under loader prompt type "unload", and than "load kernel" with required modules one by one and type "boot" at end. This will not work if malo is part of kernel itself. > Is malo known to work under 7-STABLE? I notice the man page says it > first appeared under FreeBSD 8.0. backtrace from textdump can help debugging crash, but use "kldload if_malo" after boot so that dumping can actually work, in other words use loader.conf only when you know that driver is actually stable/working. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/26/09, John wrote: > Weongyo Jeong wrote: > >> Could you please test it with attached patch to fix a page fault? I >> don't know why bus_dma_tag_create() returns ENOMEM that it looks >> temporary. > > Hi, > > Seems the patch failed to apply: Patch is so trivial and short that it can be applied manually. Are you sure that you use 7 STABLE sources and not CURRENT one? If patching failed, rebuilding module/kernel is pointless. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/26/09, John wrote: > Paul B. Mahol wrote: > >> >> Patch is so trivial and short that it can be applied manually. >> >> Are you sure that you use 7 STABLE sources and not CURRENT one? > > I'm absolutely certain. Sources from the 25th March, make world and > kernel the day after: > > [r...@potato ~]# uname -a > FreeBSD potato.growveg.org 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Thu > Mar 26 01:02:54 GMT 2009 > r...@potato.growveg.org:/usr/src/sys/amd64/compile/POTATO amd64 > [r...@potato ~]# > > my cvsupfile looks like this: > > *default host=cvsup.uk.freebsd.org > *default base=/usr > *default prefix=/usr > *default release=cvs > *default tag=RELENG_7 > *default delete use-rel-suffix > src-all > doc-all > *default tag=. This is a contradiction, I think that in csup case "last rule wins" > ports-all > >> If patching failed, rebuilding module/kernel is pointless. > > agreed > > -- > John > -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/26/09, John wrote: > Paul B. Mahol wrote: > >> This is a contradiction, I think that in csup case "last rule wins" > > How come this builds a 7-STABLE system rather than -CURRENT ? > > In any case, I appreciate your comment and will take out the offending > line. (it's in there because I thought ports was always HEAD) from csup(1) Default settings may be specified in lines whose collection name is *default. Such defaults will apply to subsequent lines in the supfile. Multiple *default lines may be present. New values augment or override any defaults specified earlier in the supfile. Values specified explic- itly for a collection override any default values. This can be much simpler. Did you noticed kernel version when you booted new kernel (available via dmesg(8))? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/27/09, John wrote: > Weongyo Jeong wrote: >> >> It looks something goes wrong so could you please patch if_malo_pci.c >> manually it's a very simple patch and test? Sorry for inconvenience. > > After editing, is it sufficient to just build and install a new kernel? Yes, (or only if_malo module if you plan to use kldload/loader.conf: cd /sys/modules/malo && make && make install) -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/28/09, John wrote: > Weongyo Jeong wrote: > >> It looks something goes wrong so could you please patch if_malo_pci.c >> manually it's a very simple patch and test? Sorry for inconvenience. > > Hello, > > Now I get: > > sudo kldload /boot/kernel/if_malo.ko > kldload: can't load /boot/kernel/if_malo.ko: Exec format error > > [j...@potato ~]$ kldstat > Id Refs AddressSize Name > 18 0x8010 7c26c0 kernel > 21 0x80a22000 95a pflog.ko > 31 0x80a23000 2ae44pf.ko > 41 0x80a4e000 189aclinux.ko > 51 0x80a67000 aa7a fuse.ko How you compiled new kernel/module? This can mean only one thing: you messed something up or you are using wrong sources. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/28/09, John wrote: > Paul B. Mahol wrote: >> On 3/28/09, John wrote: >>> Weongyo Jeong wrote: >>> >>>> It looks something goes wrong so could you please patch if_malo_pci.c >>>> manually it's a very simple patch and test? Sorry for inconvenience. >>> Hello, >>> >>> Now I get: >>> >>> sudo kldload /boot/kernel/if_malo.ko >>> kldload: can't load /boot/kernel/if_malo.ko: Exec format error >>> >>> [j...@potato ~]$ kldstat >>> Id Refs AddressSize Name >>> 18 0x8010 7c26c0 kernel >>> 21 0x80a22000 95a pflog.ko >>> 31 0x80a23000 2ae44pf.ko >>> 41 0x80a4e000 189aclinux.ko >>> 51 0x80a67000 aa7a fuse.ko >> >> How you compiled new kernel/module? >> This can mean only one thing: you messed something up or >> you are using wrong sources. >> > > It's because the other module wasn't loaded - I didn't see the console > as I was logged in remotely. > > The console showed this: > > KLD if_malo.ko: depends on malofw_fw - not available. > > So I went back into where the openbsd firmware was and kldloaded You should use this version of firmware: http://weongyo.org/project/malo/malo-firmware-1.4.tar.gz > malofw.ko which succeeded. Then I tried with the (now modified) > if_malo.ko and got this from the console: > > malo0: mem > 0xfddd-0xfddd > ,0xfdde-0xfdde irq 20 at device 6.0 on pci2 > malo0: [FILTER] > malo0: unable to allocate memory for cmd buffer, error 12 > malo0: unable to attach HAL > device_attach: malo0 attach returned 5 > > However, the modifications suggested by Weongyo Jeong have made a > difference in the right direction because the error no longer causes a > panic. > > Now, kldstat gives: > > [j...@potato ~]$ kldstat > Id Refs AddressSize Name > 1 22 0x8010 7c26c0 kernel > 21 0x80a22000 95a pflog.ko > 31 0x80a23000 2ae44pf.ko > 42 0x80a4e000 189aclinux.ko > 51 0x80a67000 aa7a fuse.ko > 61 0x80a72000 359b linprocfs.ko > 72 0x80a76000 1e1cemalofw.ko > 81 0x80a95000 63c4 if_malo.ko > 91 0x80a9c000 551b5radeon.ko > 101 0x80af2000 113d0drm.ko > > but I can't see it in ifconfig -a. > > I haven't got a source problem - of that I'm quite sure. World was made > only a few days ago, cvsup runs every night, the sources got are those > I'd expect from following RELENG_7. There is a file in the source tree > that has this information but right now I'm at a loss as to what it's > called. > -- > John > -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Boot error 16 lba
On 4/25/09, Ruben Lara wrote: > > Hi all, > > All was working fine, i reboot and now i get: > > error 16 lba 752991 > No /boot/loader > > Default: 0:ad(0,ad)/boot/kernel/kernel > > I lose my system? > What can i do? Either your hard disk is dying or something/someone corrupted loader. You can try with loader.old, type on that prompt: /boot/loader.old -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: stat() takes 54 msec in a directory with 94k files (even with a big dirhash)
On 5/12/09, Attila Nagy wrote:
> Hello,
>
> I have a strange error on FreeBSD 7-STABLE (compiled on 7th May, just
> few commits after the release, but an earlier kernel did the same).
>
> I'm doing several parallel rsyncs from a machine to another (let's call
> them source and destination). The source contains maildirs, so there are
> some directories with a (relatively) lot of files.
> The source runs an earlier (around 6.2) FreeBSD and plain softupdates
> mounted UFS2 file systems.
> The destination has a bigger (UFS2) filesystem, on top of gjournal,
> mounted as async.
>
> I've noticed that rsync sometimes stops moving data and the destination
> machine gets sluggish. After some testing, I could catch the effect in
> action (was not that hard, because it persists even for hours sometimes).
>
> top shows around 20% system activity (there are two quad core CPUs) and
> 0% user. The WCPU field at rsync shows 100%.
>
> ktrace-ing the rsync process I can see this:
>31639 rsync0.04 CALL lstat(0x7fffab70,0x7fffaf70)
>31639 rsync0.04 NAMI
> "hm33/00/16/uid/Maildir/new/1212536121.54673,S=3128"
>31639 rsync0.054226 STRU struct stat {dev=100, ino=136943662,
> mode=-rw--- , nlink=1, uid=999, gid=999, rdev=546942760,
> atime=1241807071, stime=1212536121, ctime=1241807071,
> birthtime=1212536121, size=3128, blksize=4096, blocks=8, flags=0x0 }
>31639 rsync0.13 RET lstat 0
>31639 rsync0.18 CALL lstat(0x7fffab70,0x7fffaf70)
>31639 rsync0.04 NAMI
> "hm33/00/16/uid/Maildir/new/1212537276.69702,S=4634"
>31639 rsync0.054409 STRU struct stat {dev=100, ino=136943663,
> mode=-rw--- , nlink=1, uid=999, gid=999, rdev=546942762,
> atime=1241807071, stime=1212537276, ctime=1241807071,
> birthtime=1212537276, size=4634, blksize=4096, blocks=12, flags=0x0 }
>31639 rsync0.13 RET lstat 0
>31639 rsync0.20 CALL lstat(0x7fffab70,0x7fffaf70)
>31639 rsync0.05 NAMI
> "hm33/00/16/uid/Maildir/new/1212537689.74390,S=3172"
>31639 rsync0.054230 STRU struct stat {dev=100, ino=136943664,
> mode=-rw--- , nlink=1, uid=999, gid=999, rdev=546942765,
> atime=1241807071, stime=1212537689, ctime=1241807071,
> birthtime=1212537689, size=3172, blksize=4096, blocks=8, flags=0x0 }
>31639 rsync0.13 RET lstat 0
>
> So according to ktrace, the stat call takes 54 milliseconds to return
> for each of the files.
> I have tried with the default and a pretty much raised dirhash maxmem
> value, but I can still get these.
> Currently I have:
> vfs.ufs.dirhash_docheck: 0
> vfs.ufs.dirhash_mem: 18589428
> vfs.ufs.dirhash_maxmem: 209715200
> vfs.ufs.dirhash_minsize: 2560
> So dirhash has space to expand.
>
> The directory in question contains 94493 files.
>
> The source machine doesn't show this behaviour.
>
> top's output on the destination machine:
> CPU: 0.0% user, 0.0% nice, 22.7% system, 0.0% interrupt, 77.3% idle
> Mem: 159M Active, 3032M Inact, 599M Wired, 47M Cache, 399M Buf, 102M Free
> Swap: 4096M Total, 4096M Free
>
> PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND
> 31639 root 1 1180 50648K 10512K CPU0 0 2:01 100.00% rsync
> 634 root 1 -40 2536K 628K vlruwk 1 0:20 0.00% supervise
> 26760 root 1 440 25940K 3316K select 1 0:10 0.00% sshd
> 31640 root 1 750 87512K 8324K suspfs 4 0:10 0.00% rsync
> 31641 root 1 750 18904K 7124K suspfs 6 0:10 0.00% rsync
> 31637 root 1 750 40408K 7744K suspfs 4 0:09 0.00% rsync
> 31636 root 1 440 20952K 6288K select 2 0:09 0.00% rsync
> 31638 root 1 440 104M 8912K select 3 0:09 0.00% rsync
> 31635 root 1 750 80344K 7812K suspfs 4 0:09 0.00% rsync
> 31642 root 1 440 17940K 7624K select 1 0:04 0.00% ssh
> 31646 root 1 450 17940K 7656K select 1 0:03 0.00% ssh
>
> All of the rsyncs use the same file system, but with different top level
> directories. During this, neither of the other rsyncs can run.
>
> Any ideas about what could be done to work around this?
Big guess, maybe it updates atime? Try with noatime mount option.
--
Paul
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fear and loathing in FreeBSD 7.2 (AGP issues and fixes)
On 5/17/09, Bill Paul wrote:
>
> So. I decided to test FreeBSD 7.2 on my Averatec AV1020 ED1 laptop. (It
> currently has 6.0-RELEASE on it, and while it runs fine, I figured now
> was a good time to update it.) I ran into two problems with it, and I
> thought it would be a good idea to share how I resolved them, just in
> case anyone else is foolish enough to follow in my tracks.
>
> The laptop has a RaLink RT2560 wireless chipset. The ral(4) driver
> supports this chip out of the box, however that driver doesn't support
> WPA2 Enterprise, which I need for work. To get around this, I use
> the Windows NDIS driver with Project Evil. Unfortunately, the driver
> that comes with the laptop (version 3.0.3.) is buggy, and will
> trigger a kernel panic in certain conditions. It seems to have trouble
> parsing information from certain newer kinds of devices, which causes
> some of the code inside the driver binary to dereference a bogus pointer.
>
> This is not a problem with FreeBSD or Project Evil: I discovered that
> the same driver blue-screens Windows XP as well (a testament to just
> how closely Project Evil emulates Windows: it even emulates its crashes).
> Luckily there is a slightly newer driver available that fixes this issue
> (3.1.0.000), though I had to hunt a bit to find it. I put copies of
> the .SYS and .INF at:
>
> http://www.freebsd.org/~wpaul/7_2_RELEASE/wifi
>
> The other problems I had were with graphics. The Averatec has an Intel
> 82855GME graphics controller. With FreeBSD 6.0, I had it working nicely
> with DRI and everything. With FreeBSD 7.2 and xorg 1.6.0, I saw some
> peculiar problems.
>
> The most glaring issue was that after running X -configure for the first
> time and testing the resulting xorg.conf file, I found that the X server
> would not respond to the mouse or keyboard. After some digging, I found
> that this was due to the AutoAddDevices feature (described in xorg.conf(5))
> being on by default. If AutoAddDevices is on, then AllowEmptyInput is also
> turned on, but the description for AllowEmptyInput says: "If AllowEmptyInput
> is on, devices using the kbd, mouse or vmmouse driver are ignored." I
> don't know what's supposed to happen instead, but it wasn't working. I
> had to add:
>
> Option "AutoAddDevices" "False"
>
> to my xorg.conf to turn this off in order for my mouse and keyboard to
> work.
>
> On a related note, the X server seems to ignore a lot of what you put
> in xorg.conf in favor of its autoselected defaults. I tried to use
> "DefaultDepth 24" to force the screen color depth, but it seems to
> always ignore this and use a depth of 32 bits. It seems to work ok, but
> I thought this was odd. If I tell it to do something, it should do it.
> This used to work in earlier X releases.
Well, at least with intel driver on i915GM using anything lower than
defaults will cause interesting artefacts on various games: alephone & oolite.
>
> More curiously, X -configure decided for some reason that my laptop
> had two graphics cards instead of one. This apparently has to do with
> the fact that the gracphic device has two PCI functions:
>
> vgap...@pci0:0:2:0: class=0x03 card=0x031914ff chip=0x35828086
> rev=0x02 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82852GM/GME/GMV/PM, 855GM/GME Montara Integrated Graphics
> Device'
> class = display
> subclass = VGA
> vgap...@pci0:0:2:1: class=0x038000 card=0x031914ff chip=0x35828086
> rev=0x02 hdr=0x00
> vendor = 'Intel Corporation'
> device = '82852GM/GME/GMV/PM, 855GM/GME Montara Integrated Graphics
> Device'
> class = display
>
> X -configure created a "Card" and "Screen" section for both of these, even
> though it should only have created one. I had to edit the xorg.conf to
> remove the duplicates. (This was something else that worked correctly in
> older versions of X.)
>
> Once I settled those issues, the X server worked, but I found that I
> was unable to use DRI. FreeBSD was correctly loading the agp, drm and
> i915 drivers, but the X server refused to activate DRI support. According
> to the Xorg.log.0 file, it was failing to allocate a couple of regions
> of physical memory from the AGP driver. I finally traced this down to
> the agp_i810 code in the kernel. In agp_i810_alloc_memory(), it says:
>
> [...]
> } else if (type == 2) {
> /*
> * Type 2 is the contiguous physical memory type, that hands
> * back a physical address. This is used for cursors on
> i810.
> * Hand back as many single pages with physical as the user
> * wants, but only allow one larger allocation (ARGB cursor)
> * for simplicity.
> */
> if (size != AGP_PAGE_SIZE) {
> if (sc->argb_cursor != NULL)
> return 0;
>
> [...]
>
> I'm all for simplicity, but this i
Re: Fear and loathing in FreeBSD 7.2 (AGP issues and fixes)
On 5/17/09, Paul B. Mahol wrote: > On 5/17/09, Bill Paul wrote: >> >> So. I decided to test FreeBSD 7.2 on my Averatec AV1020 ED1 laptop. (It >> currently has 6.0-RELEASE on it, and while it runs fine, I figured now >> was a good time to update it.) I ran into two problems with it, and I >> thought it would be a good idea to share how I resolved them, just in >> case anyone else is foolish enough to follow in my tracks. >> >> The laptop has a RaLink RT2560 wireless chipset. The ral(4) driver >> supports this chip out of the box, however that driver doesn't support >> WPA2 Enterprise, which I need for work. To get around this, I use >> the Windows NDIS driver with Project Evil. Unfortunately, the driver >> that comes with the laptop (version 3.0.3.) is buggy, and will >> trigger a kernel panic in certain conditions. It seems to have trouble >> parsing information from certain newer kinds of devices, which causes >> some of the code inside the driver binary to dereference a bogus pointer. >> >> This is not a problem with FreeBSD or Project Evil: I discovered that >> the same driver blue-screens Windows XP as well (a testament to just >> how closely Project Evil emulates Windows: it even emulates its crashes). >> Luckily there is a slightly newer driver available that fixes this issue >> (3.1.0.000), though I had to hunt a bit to find it. I put copies of >> the .SYS and .INF at: >> >> http://www.freebsd.org/~wpaul/7_2_RELEASE/wifi >> >> The other problems I had were with graphics. The Averatec has an Intel >> 82855GME graphics controller. With FreeBSD 6.0, I had it working nicely >> with DRI and everything. With FreeBSD 7.2 and xorg 1.6.0, I saw some >> peculiar problems. >> >> The most glaring issue was that after running X -configure for the first >> time and testing the resulting xorg.conf file, I found that the X server >> would not respond to the mouse or keyboard. After some digging, I found >> that this was due to the AutoAddDevices feature (described in >> xorg.conf(5)) >> being on by default. If AutoAddDevices is on, then AllowEmptyInput is >> also >> turned on, but the description for AllowEmptyInput says: "If >> AllowEmptyInput >> is on, devices using the kbd, mouse or vmmouse driver are ignored." I >> don't know what's supposed to happen instead, but it wasn't working. I >> had to add: >> >> Option "AutoAddDevices" "False" >> >> to my xorg.conf to turn this off in order for my mouse and keyboard to >> work. >> >> On a related note, the X server seems to ignore a lot of what you put >> in xorg.conf in favor of its autoselected defaults. I tried to use >> "DefaultDepth 24" to force the screen color depth, but it seems to >> always ignore this and use a depth of 32 bits. It seems to work ok, but >> I thought this was odd. If I tell it to do something, it should do it. >> This used to work in earlier X releases. > > Well, at least with intel driver on i915GM using anything lower than > defaults will cause interesting artefacts on various games: alephone & > oolite. > >> >> More curiously, X -configure decided for some reason that my laptop >> had two graphics cards instead of one. This apparently has to do with >> the fact that the gracphic device has two PCI functions: >> >> vgap...@pci0:0:2:0: class=0x03 card=0x031914ff chip=0x35828086 >> rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82852GM/GME/GMV/PM, 855GM/GME Montara Integrated >> Graphics >> Device' >> class = display >> subclass = VGA >> vgap...@pci0:0:2:1: class=0x038000 card=0x031914ff chip=0x35828086 >> rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82852GM/GME/GMV/PM, 855GM/GME Montara Integrated >> Graphics >> Device' >> class = display >> >> X -configure created a "Card" and "Screen" section for both of these, >> even >> though it should only have created one. I had to edit the xorg.conf to >> remove the duplicates. (This was something else that worked correctly in >> older versions of X.) >> >> Once I settled those issues, the X server worked, but I found that I >> was unable to use DRI. FreeBSD was correctly loading the agp, drm and >> i915 drivers, but the X server refused to activate DRI support. According >> to the Xorg.log.0 file, it was failing to allocate a co
Re: failed to set mtrr: invalid argument
On 5/19/09, Chris H wrote: > Quoting Chris H : > >> Quoting Chris H : >> >>> Greetings, >>> I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440. >>> On 7.1-7.2 releases. I'm currently working (struggling) with >>> it on a 7.1 install/GENERIC with cvsup over the weekend (Sunday), >>> I've seen only a few discussions regarding this, but no joy. >>> >>> I'm not sure what to post for additional information. So I'll >>> provide the output of dmesg(8), and Xorg.0.log via links. >>> >>> Thank you for all your time and consideration in this matter. >>> >>> Sincerely, >>> Chris H >>> >>> Xorg log: >>> http://codewarehouse.NET/output/Xorg.0.log >>> >>> relevent dmesg(8) output: >>> http://codewarehouse.NET/output/dmesg.output >> >> OOPS! I guess the xorg config might be useful: >> http://codewarehouse.NET/output/xorg.conf.nvidia >> >>> > SIGH... Seems that the registrar isn't paying attention. > They happily accepted my money, but forgot to renew the domain. > > So here's trying to attach the files... That message appears for me only when I use xf86-video-vesa driver. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: failed to set mtrr: invalid argument
On 5/19/09, Dimitry Andric wrote: > On 2009-05-19 08:40, Chris H wrote: >> I see. Well I'm specifically using the nv driver. Here's another >> attempt to provide the relevant info: > > I could not find the error message from $subject in these logs. Where > is it? :) In thread subject. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: failed to set mtrr: invalid argument
On 5/20/09, Robert Noland wrote: > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: >> > So, zapping is off by default now in 1.6.x. If you want it, add >> Option >> > "DontZap" "off". The cross hatch is also gone, that is what the >> -retro >> > option is supposed to do. The session leader in a failsafe twm >> session >> > is the left hand xterm. Typing exit in that window should exit the >> > session. >> >> DOH! Sorry. My bad. I have since determined that turning off hald && >> dbus >> improve performance. I built the X server with the hald option picked. >> But, when I bounced the box, and started an X session (with a WM), >> performance was improved. BUT. Performance pretty much sucks. I have 4 >> of these boards running with the onbord (mach64) video, and the mere >> 2Mb >> built in RAM. They run with better performance than does this one with >> (200Mhz less CPU) comparable RAM && this one has 64Mb onboard && a >> faster >> Gpu. But they also run 6.4-STABLE && xorg-6.9. >> So, I'm going to experiment by rebuilding the X server w/o the HAL >> driver - make option && untick HAL. Then portupgrade -fi xorg-server. >> >> I'll report back should there be any improvement. > > So, the use of hal or not shouldn't produce any performance difference. > It is only used to detect input devices kbd/mouse. > > One thing that I have discovered and I'm hoping for someone to send me a > patch, is that if you build xorg-server without hal support it doesn't > get linked to pthread libraries. This causes issues with libdrm on > Intel at least. Not sure what else may be impacted. I ignored this info first time, but I will ask now. Does this implies that libthr is listed in Xorg ldd(1) output? I use server build without hal support on 945GM(irq not MSI) and I do not experience problems with drm/dri/OpenGL/xv or whatever other protocol you name it. > There is also my nouveau patch that you could try. That should get you > EXA and Xv acceleration with the nouveau driver. Overall the reports > that I've been getting have been good. > > robert. > >> Thank you very much Robert, for all your time and efforts. > -- > Robert Noland > FreeBSD > -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: failed to set mtrr: invalid argument
On 5/20/09, Robert Noland wrote: > On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote: >> On 5/20/09, Robert Noland wrote: >> > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote: >> >> > So, zapping is off by default now in 1.6.x. If you want it, add >> >> Option >> >> > "DontZap" "off". The cross hatch is also gone, that is what the >> >> -retro >> >> > option is supposed to do. The session leader in a failsafe twm >> >> session >> >> > is the left hand xterm. Typing exit in that window should exit the >> >> > session. >> >> >> >> DOH! Sorry. My bad. I have since determined that turning off hald && >> >> dbus >> >> improve performance. I built the X server with the hald option picked. >> >> But, when I bounced the box, and started an X session (with a WM), >> >> performance was improved. BUT. Performance pretty much sucks. I have 4 >> >> of these boards running with the onbord (mach64) video, and the mere >> >> 2Mb >> >> built in RAM. They run with better performance than does this one with >> >> (200Mhz less CPU) comparable RAM && this one has 64Mb onboard && a >> >> faster >> >> Gpu. But they also run 6.4-STABLE && xorg-6.9. >> >> So, I'm going to experiment by rebuilding the X server w/o the HAL >> >> driver - make option && untick HAL. Then portupgrade -fi xorg-server. >> >> >> >> I'll report back should there be any improvement. >> > >> > So, the use of hal or not shouldn't produce any performance difference. >> > It is only used to detect input devices kbd/mouse. >> > >> > One thing that I have discovered and I'm hoping for someone to send me a >> > patch, is that if you build xorg-server without hal support it doesn't >> > get linked to pthread libraries. This causes issues with libdrm on >> > Intel at least. Not sure what else may be impacted. >> >> I ignored this info first time, but I will ask now. Does this implies >> that libthr is listed in Xorg ldd(1) output? >> >> I use server build without hal support on 945GM(irq not MSI) and I do >> not experience problems with drm/dri/OpenGL/xv or whatever other >> protocol you name it. > > Yes, if xserver is built with HAL support, I see it linked with libthr. > If HAL is disabled, it doesn't appear to be. I'm trying to remember > exactly what the reported issue was, but I think it was X crashing on > exit. Looking at xorg-server source I did not see anything that points it must link to libthr, perhaps HAL support makes libthr linking mandatory. X doesnt crash on exit for me, well it did before (maybe because drm outputs ressurected *pipe disabled* message on console all the time). Should this finnaly be replaced with DRM_DEBUG ? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: malo wireless driver - is this capable of wpa2-personal (WPA2-PSK)
On 6/11/09, John wrote: > Hello list, > > uname -prs > FreeBSD 7.2-RELEASE-p1 amd64 > > Question as subject, really. Is the malo driver capable of WPA2 under > FreeBSD? ? If so, how would it be set? I've tried various wireless via wpa_supplicant(8) > options via ifconfig, can't seem to get it to work, so am wondering if > it is capable of it. I know support for it appeared in HEAD on OpenBSD > around the middle of April, and this driver is derived from that. > > thanks > -- > John > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Something since June 8th clobbers my disk...
On 6/11/09, Dan Allen wrote: > I sync with 7-STABLE almost every day. I build everything on a > Toshiba U205 Satellite. Things are fine for months on end. > > I did this on June 8th. Everything was fine. > > I did this on June 10th. The machine no longer booted. The entire > root partition got clobbered. I reinstalled a snapshot of 7-STABLE > from May 28th that I had put on a DVD. Everything was once again fine. > > I then sync'd again this morning June 11th with 7-STABLE, did a full > build, and reproducibly, BOOM - the entire root partition got > clobbered. Gone. Again. After the reboot it just comes up with: > > BTX loader 1.00 BTX version is 1.02 > Consoles: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > > and stops. Nothing else is printed. There is no choice of how to > boot. There is no files for me to send, no log files to inspect, no > remnants. I unfortunately did not see where in the build this > happened. My build does the canonical steps exactly as outlined in / > usr/src/Makefile and then does a reboot. It builds userland and the > kernel. > > When I inspect it from the bootable DVD the partition that my root > filesystem was in has no association with it having the root any > more. The partition is listed, but it looks like it had been freshly > partitioned. > > Something is very, very wrong. > > Ideas? Are you using ZFS on root partition? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Something since June 8th clobbers my disk...
On 6/11/09, Dan Allen wrote: > Okay. I did a > > make buildkernel && installkernel > > and rebooted, no problems. > > I then did a > > make buildworld > > and rebooted, no problems. > > I then did a > > make installworld > > which completed normally, rebooted, and > > BINGO - my disk partition table has been zapped. > > The problem appears to be something that runs during this 'make > installworld'! > > There are no problems with the build itself that I can tell, but some > program is munging the disk partition table. > > In a zany sort of way this is progress. Of course now I have to > reinstall the OS, again... Looks like boot(8) is problematic. Anything in /etc/src.conf or /etc/make.conf? -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Something since June 8th clobbers my disk...
On 6/13/09, Dan Allen wrote: > > On 12 Jun 2009, at 6:32 AM, John Baldwin wrote: > >> On Thursday 11 June 2009 9:33:24 pm Dan Allen wrote: >>> Isn't boot part of the kernel build? Why would installing the kernel >>> not cause this problem? >> >> No, sys/boot is built during world. Likely some change in /boot/ >> loader is >> causing your problem. Can you narrow it down to a specific change >> under >> sys/boot? > > Ok. I updated just the one file since it appeared like one of the few > changed files > > /usr/src/sys/boot/i386/libi386/biosdisk.c > > and rebuilt things with > > cd /usr/src/sys/boot; make cleandir obj depend all install > > and it was okay. No problems. > > Then I did sync'd all of the changed files for /usr/src/sys/boot and > my machine is hung again at boot, so we have narrowed it down to > somewhere in /usr/src/sys/boot/. > > Time to reinstall from a DVD and try it with finer granularity. This > will take some time. > > There appears to be only four files that have changed in /usr/src/sys/ > boot from June 8th (all working fine) to June 11th (dead in the > water). They are: > > /usr/src/sys/boot/Makefile > /usr/src/sys/boot/i386/Makefile > /usr/src/sys/boot/i386/libi386/biosdisk.c I doubt it is loader fault, from your description it appears that loader is never started. Could you try to remove -DLOADER_ZFS_SUPPORT from Makefile? > /usr/src/sys/boot/i386/loader/Makefile > > I have ruled out bisodisk.c, as stated above. > > That means that the Makefiles are building new stuff that previously > was not built, namely > > zfsboot gptzfsboot > > I believe it has to do with that. More help is needed! I am tired of > reinstalling the OS, but I am much more paranoid about updating my > other machine in any way now, as it could erase that whole machine. I > can't believe I am the only one seeing this... > > Dan > > -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Let's back out LOADER_ZFS_SUPPORT from STABLE
On 6/13/09, Dan Allen wrote: > I have now proven that the recent post June 8th version of > > /usr/src/sys/boot/i386/loader/Makefile > > causes catastrophic data loss. > > Why on earth would this change not be immediately rolled back out of > the STABLE branch? For those on the bleeding edge with CURRENT they > expect to lose their entire drives, but not STABLE users. I hardly doubt that such change cause loss of data on entire drive. There is always old loader to pick up. > We need to remove -DLOADER_ZFS_SUPPORT from /usr/src/sys/boot/i386/ > loader/Makefile immediately. I don't understand why LOADER_ZFS_SUPPORT is not defined by default on CURRENT. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kernel wants the wrong driver for my NIC (new issue)
On 6/20/09, Michael Gass wrote: > On Fri, Jun 19, 2009 at 12:24:29PM -0500, Michael Gass wrote: >> I'm running 7.2-stable and I replaced an old ISA NIC with >> a D-Link DFE-530TX+ card. According to the manual, the >> correct driver for this card is rl driver. The kernel >> insists on using the vr driver which is for the DFE-530TX. >> >From what I can tell, the two cards have different chipsets >> and so the drivers are not compatable. >> > > I got the vr driver to work: it was an IRQ issue. Seems > sio1 wanted irq 3 which is what vr0 was taking. Somehow that > caused a problem. > > BUT > > I am still confused about the rl driver not working for this > card. The NOTES in /usr/src/sys/conf/NOTES explicitly state > that the rl driver is for the DFE-530TX+ and that the vr > driver is for the DFE-530TX. I have the former and so should > be using the rl drive it seems. Is this a mistake in the > documentation (including the man page for each driver)? > > I made a new kernel without the vr driver and the result was > that no driver at all was recognized for the NIC. > Is there a way to force the kernel to put an entry in /dev > for rl0 so that I could try to configue it for the NIC? Yes, modify source code and recompile and reinstall/kldload kernel/module. -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: hostapd "deauthenticated due to local deauth request"
On 10/31/09, Ivan Voras wrote: > I'm trying to setup an AP with a run0 interface on latest 8-STABLE but > apparently 802.11 association fails: > > Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > > etc. Apparently the client never comes to the phase to receive DHCP address. > > The client in this case is WinXP and the setup did work with 7-STABLE, > though with a bug in the rum driver which caused regular kernel panics > on the AP. > I tried same one with rum(4) as AP and ndis(4) as client on same machine(some version of 8.0 - CURRENT). ndis client (configured via wpa_supplicant) would keep auth and deauth all the time. I came to conclusion that rum is broken. But I think I remmember that bwi(4) (as a client) did not have such problem ... (I will test again to see) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: hostapd "deauthenticated due to local deauth request"
On 10/31/09, Paul B Mahol wrote: > On 10/31/09, Ivan Voras wrote: >> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but >> apparently 802.11 association fails: >> >> Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> >> etc. Apparently the client never comes to the phase to receive DHCP >> address. >> >> The client in this case is WinXP and the setup did work with 7-STABLE, >> though with a bug in the rum driver which caused regular kernel panics >> on the AP. >> > > I tried same one with rum(4) as AP and ndis(4) as client on same > machine(some version of 8.0 - CURRENT). ndis client (configured via > wpa_supplicant) > would keep auth and deauth all the time. > I came to conclusion that rum is broken. But I think I remmember that > bwi(4) (as a client) > did not have such problem ... (I will test again to see) Well, I tried again and I got similar output like yours if I use wrong password. And with correct password client reauth all the time, maybe I need to setup ndis_events(8) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
