Re: NFS UDP mounts on RELENG_6?
On Mon, 2005-Dec-19 08:39:47 +0100, Oliver Brandmueller wrote: While NFS stalls at the same time ntp to the same host works without problems. So it's not a comüplete stall of all UDP traffic.I guess there's something that's only triggered by a certain combination of things. How about big/fragmented UDP packets? NFS typically sends 8K packets which are split into 6 UDP packets. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS UDP mounts on RELENG_6?
A very critical question here is the network topology. UDP NFS _cannot_ be used across switches where the ports are operating at different speeds--unless the UDP packet size is to be smaller than MTU. Be sure and verify that every link between the server and the client are operating at the same speed. -Jon On Sun, 18 Dec 2005, Fabian Keil wrote: Oliver Brandmueller [EMAIL PROTECTED] wrote: On Fri, Dec 16, 2005 at 04:30:31PM +0100, Fabian Keil wrote: Oliver Brandmueller [EMAIL PROTECTED] wrote: I'm experiencing problems when trying to mount NFS filesystems from a RELENG_6 server (FreeBSD hudson 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Dec 14 16:59:55 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NFS-32-FBSD6 i386) to either 5.4-STABLE or 6-STABLE clients. mounting works fine, but afterwards the access to the filesystem on the client stalls. As soon as I mount the FS with a TCP mount everything works as expected. The mounts worked fine on UDP when the server was 5.4-STABLE. There is just a plain GigE switch involved, no firewalls or routing. Anyone else experiencing those problems or having an idea? I just copied some files (200 MB) from a NFS Server running FreeBSD africanqueen.local 6.0-STABLE FreeBSD 6.0-STABLE #5: Thu Dec 15 19:31:12 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AFRICANQUEEN i386 without problems. My client runs FreeBSD 5.4, I use GigE as well, but no switch. Which kind GigE Interface do you use? Client: [EMAIL PROTECTED] ~ $pciconf -lv| grep em0 -A 2 [EMAIL PROTECTED]:1:0: class=0x02 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' Server: [EMAIL PROTECTED] ~ $pciconf -lv| grep re[01] -A 2 [EMAIL PROTECTED]:9:0: class=0x02 card=0x816910ec chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' -- [EMAIL PROTECTED]:10:0: class=0x02 card=0x601b182d chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' re0 is made by Vivanco, re1 is a Sitecom card. Fabian -- http://www.fabiankeil.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: NFS UDP mounts on RELENG_6?
Hi. On Mon, Dec 19, 2005 at 01:01:34AM -0800, Jon Dama wrote: A very critical question here is the network topology. UDP NFS _cannot_ be used across switches where the ports are operating at different speeds--unless the UDP packet size is to be smaller than MTU. Be sure and verify that every link between the server and the client are operating at the same speed. *ouch* shame on me. I looked at interfaces, links, errors - everything. I found the problem in a misconfiguration and you just pointed at it: The server has not been booted for a few hundred days before upgrading. From an old test there was an mtu 9000 for the NFS interface still in /etc/rc.conf (while it has been reset after failed tests with other hardware on that network manually to 1500). So: SORRY for making everybody mad here. It was just me being blind. Thanx for pointing me at that! - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: NFS UDP mounts on RELENG_6?
No shame. This is a common problem, and if you think real hard you should start getting quasy about UDP NFS under high load. The problem arises because if part of a UDP packet is lost the entire packet is lost, and as UDP NFS uses fixed packet sizes... this means the system never recovers if frames stop droping perpetually. Its easy to see how this happens for speed mismatches, the switch (vs a router) provides no buffering and therefore frames from the fast source are dropped. Now imagine that you have many clients all writing data to the NFS server at once... Suddently that pipe into the server is like a narrow straw. Ooops. I haven't see any evidence that suggests using NFS with UDP is actually useful. IMO, its a false economy. TCP processing takes on the order of 1uS of CPU time--which is on the order of the frame latency through a single switch! That is to say, nothing, but the behavior of TCP NFS under load (when it counts) is superior. TCP SACK and interrupt aggregation are better ways of squeezing extra performance out of your hardware than simply using UDP... Just my two cents. -Jon On Mon, 19 Dec 2005, Oliver Brandmueller wrote: Hi. On Mon, Dec 19, 2005 at 01:01:34AM -0800, Jon Dama wrote: A very critical question here is the network topology. UDP NFS _cannot_ be used across switches where the ports are operating at different speeds--unless the UDP packet size is to be smaller than MTU. Be sure and verify that every link between the server and the client are operating at the same speed. *ouch* shame on me. I looked at interfaces, links, errors - everything. I found the problem in a misconfiguration and you just pointed at it: The server has not been booted for a few hundred days before upgrading. From an old test there was an mtu 9000 for the NFS interface still in /etc/rc.conf (while it has been reset after failed tests with other hardware on that network manually to 1500). So: SORRY for making everybody mad here. It was just me being blind. Thanx for pointing me at that! - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DLT Tape Read errors on aac0
Scott Long schrieb: First of all, let me apologize for the mess that is the aac passthrough driver. I wrote it in hopes that it would be useful, but the support needed for it in the aac firmware simply isn't robust enough for the kind of SCSI stuff that FreeBSD does. In other words, it's a hack from top to bottom, and really is little more than a novelty at this point. See below... Christian Gründemann wrote: Waah, I forgot the most important information. Its an 5.3-STABLE FreeBSD Operating System. :-) Christian Christian Gründemann schrieb: Hi, I am using an Adaptec SCSI RAID 2120S Card with 5 SCSI Seagate drives as a RAID-5 without any probelms for almost two years now. Last week I attached to the aac0 controller a Tandberg DLT Drive QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device for large backup purposes. We decided to use dump/restore for our backup strategy but unfortunately we can only make backups and no restores. E.g dumping a filesystem works great: [EMAIL PROTECTED] ~ dump -0aLf /dev/sa0 /var DUMP: Date of this level 0 dump: Tue Dec 20 15:44:05 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/aacd0s1f (/var) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 63220 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 64341 tape blocks on 1 volume DUMP: finished in 15 seconds, throughput 4289 KBytes/sec DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE [EMAIL PROTECTED] ~ I guess the backup has been successfully finished. But when I try a access the backup ether via the interactive console or by trying to extract the data directly I get the follwing errors in /var/log/messages [EMAIL PROTECTED] /var restore -i -f /dev/sa0 tape read error: Input/output error Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): READ(06). CDB: 8 0 0 80 0 0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): NO SENSE ILI (length mismatch): 22528 csi:e0,40,0,20 asc:0,0 Dec 20 15:49:22 hercules kernel: (sa0:aacp0:0:5:0): No additional sense information This is very very strange, and I don't even know where to start guessing. It could be either a fairly minor bug in the driver, or a major bug/lack of support in the firmware. Sometimes I often get some Timeouts (only using restore). Dec 19 11:34:27 hercules kernel: aac0: COMMAND 0xc1fdf750 TIMEOUT AFTER 51 SECONDS This is usually a sign that the firmware either lost a command, or paniced all together. Both conditions are fatal =-( Kernel config: - # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device aac # Adaptec FSA RAID device aacp# SCSI passthrough for aac (requires CAM) - dmesg (cutted): -- hercules kernel: CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2399.33-MHz 686-class CPU) hercules kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs hercules kernel: cpu0 (BSP): APIC ID: 0 hercules kernel: cpu1 (AP): APIC ID: 1 hercules kernel: cpu2 (AP): APIC ID: 6 hercules kernel: cpu3 (AP): APIC ID: 7 aac0: Adaptec SCSI RAID 2120S mem 0xd000-0xd3ff irq 52 at device 2.0 on pci4 aac0: [FAST] aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N bd10c2 aac0: Supported Options=11d7eCLUSTERS,WCACHE,DATA64,HOSTTIME,RAID50,WINDOW4GB,SOFTERR,SGMAP64,ALARM,NONDASD aacp0: SCSI Passthrough Bus on aac0 acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% (probe5:aacp0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe5:aacp0:0:5:0): NOT READY csi:e0,40,0,1c asc:4,1 (probe5:aacp0:0:5:0): Logical unit is in process of becoming ready sa0 at aacp0 bus 0 target 5 lun 0 sa0: QUANTUM DLT VS160 2500 Removable Sequential Access SCSI-2 device sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) -- Does anybody maybe have an idea why I can use dump but not restore ? This doesn't make sense to me. And I should mention that tar works great! I can write and read from the tape, even with filemarks. Thanks for your help! Christian I have a DLT drive here that I could probably hook up and start debugging with, but there are a lot of other things on my plate with higher priority, unfortunately. Your best bet for now is to put the tape drive onto a real Symbios or Adaptec SCSI card. Scott Thanks for your fast answer, Scott! What Adaptec Card
ПРИВЕТ ПРОВЕРКА СВЯЗ И
? ?!! ? ? ? -- amar ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-stable doesn't recognize detatchment of CD-Rom
I don't know into which list this belongs, so I'm posting it to mobile and stable. I've got a Thinkpad-R40, a first generation Centrino system. When I detach the CD-Rom drive nothing is shown on dmesg. The same when I reenter it. No dmesg output. When I try to mount a cd after detaching and reentering the drive the system freezes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: NFS UDP mounts on RELENG_6?
On Mon, 2005-Dec-19 01:37:44 -0800, Jon Dama wrote: I haven't see any evidence that suggests using NFS with UDP is actually useful. IMO, its a false economy. On modern hardware anyway. Keep in mind that NFS was written to run on a 25MHz (or so) 68020. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: NFS UDP mounts on RELENG_6?
I haven't see any evidence that suggests using NFS with UDP is actually useful. IMO, its a false economy. On modern hardware anyway. Keep in mind that NFS was written to run on a 25MHz (or so) 68020. 100% agreed. That is precisely what assumed when I made my statement. -Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i915drm
Le Dimanche 18 Décembre 2005 01:31, Gianmarco a écrit : I am trying to use the latest drm hook for i915, but I get this error: drmsub0: Intel i915GM port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) Any idea ? I have added to my kernel: device agp # support several AGP chipsets device drm # DRM core module required by DRM drivers device i915drm # Intel i830 through i915 Just put agp, Xorg will load i915.ko. I've got the same problem. But dri does not work, Xorg seems to look for a /dev/dri/card0 and i've got only one device /dev/dri/card1 ? Xorg.log: (II) I810(0): Allocated 64 kB for the scratch buffer at 0x7fee000 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module i915 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Acer Ferrari 4005 WMLi Configuration Files
Dear Reader, If you have a Ferrari 4005 WMli and you made work with the FreeBSD 6.0 64bit Release, please do not hesitate to share you config files with me, since i have a tough time in configuring the system so far. I need the files Regarding the Kernel Settings and the Xorg settings since i use the windowmaker as my windowmanager. thank you in advanced -- Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Re: NFS UDP mounts on RELENG_6?
On Mon, Dec 19, 2005 at 09:04:46PM +1100, Peter Jeremy wrote.. On Mon, 2005-Dec-19 01:37:44 -0800, Jon Dama wrote: I haven't see any evidence that suggests using NFS with UDP is actually useful. IMO, its a false economy. On modern hardware anyway. Keep in mind that NFS was written to run on a 25MHz (or so) 68020. Sun2, 68010 ;) -- Wilko Bulte [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: Fast releases demand binary updates.. (Was: Release schedule for 2006)
On Sun, Dec 18, 2005 at 12:13:09PM -0500, Kris Kennaway wrote: Doesn't creating a binary updates system that's going to be practical to use require implementation of that old and exceedingly bikesheddable subject: packaging up the base system? No, after all the *existing* binary update systems don't require packaging of the base system. Except that the existing binary update system is broken in several fundamental ways. I guess the reason it gets little attention is because most developers are happy to (or even prefer to) rebuild their systems from source. Regards, Brian. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0/amd64 boot hang if apic enabled on IBM x336
Hi all, We have a IBM xSeries 336 which has 2 Pentium 4 (EM64T) 3.2G with 2GB memory. When we boot it with 6.0-RELEASE/amd64, it hangs after acd0 is shown. However, if apic is disabled, then it boots. For 5.4-RELEASE/amd64, it works great. A 7.0-CURRENT (SNAP009, Nov/2005) shows the same behavior. To have it boot, I set following in loader.conf hint.atkbd.0.disabled=0x4 # otherwise, I lose my keyboard hint.apic.0.disabled=1 The verbose dmesg with/without apic, and the asl dump (with bios version 1.12, the latest one found on IBM site) are available at: http://www.rafan.org/FreeBSD/x336/ BTW, the SCSI timeout message from dmesg-noapic.txt is a bit wired. If I boot without verbose message it does not show, everything works great. With verbose booting, those messages show up and it takes me a lot of time to get into multiuser mode. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Acer Ferrari 4005 WMLi Configuration Files
mm If you have a Ferrari 4005 WMli and you made work with the mm FreeBSD 6.0 64bit Release, please do not hesitate to share mm you config files with me, since i have a tough time in mm configuring the system so far. It would help if you could tell us where you've managed to reach so far. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0/amd64 boot hang if apic enabled on IBM x336
I'm run FreeBSD 6.0-RELEASE hint.acpi.0.disabled=1 in /boot/device.hints and options SMP options IPI_PREEMPTION device mptable and device atpic commented out in custom kernel The hardware is single 3.0GHz CPU and 4GB RAM. The question I have. Does Intel CPU have HTT in amd64 mode? Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] On Mon, 19 Dec 2005, Rong-En Fan wrote: Hi all, We have a IBM xSeries 336 which has 2 Pentium 4 (EM64T) 3.2G with 2GB memory. When we boot it with 6.0-RELEASE/amd64, it hangs after acd0 is shown. However, if apic is disabled, then it boots. For 5.4-RELEASE/amd64, it works great. A 7.0-CURRENT (SNAP009, Nov/2005) shows the same behavior. To have it boot, I set following in loader.conf hint.atkbd.0.disabled=0x4 # otherwise, I lose my keyboard hint.apic.0.disabled=1 The verbose dmesg with/without apic, and the asl dump (with bios version 1.12, the latest one found on IBM site) are available at: http://www.rafan.org/FreeBSD/x336/ BTW, the SCSI timeout message from dmesg-noapic.txt is a bit wired. If I boot without verbose message it does not show, everything works great. With verbose booting, those messages show up and it takes me a lot of time to get into multiuser mode. Regards, Rong-En Fan ___ 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: 6.0/amd64 boot hang if apic enabled on IBM x336
mk The question I have. Does Intel CPU have HTT in amd64 mode? Yes, AFAIK. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: lockmgr: locking against myself
Hi, On 12/19/05, Mathieu Arnold [EMAIL PROTECTED] wrote: Unread portion of the kernel message buffer: panic: lockmgr: locking against myself Is it 6.0-RELEASE and you have mounted NFS? Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: lockmgr: locking against myself
+-le 20/12/2005 00:00 +0800, Xin LI a dit : | Hi, | | On 12/19/05, Mathieu Arnold [EMAIL PROTECTED] wrote: | Unread portion of the kernel message buffer: | panic: lockmgr: locking against myself | | Is it 6.0-RELEASE and you have mounted NFS? Both, yes. -- Mathieu Arnold pgpUsosxto9Zj.pgp Description: PGP signature
Re: Release Schedule for 2006
On Sun, Dec 18, 2005 at 12:06:12PM -0500, Kris Kennaway wrote: Well, no, the sound system is not broken, perhaps a driver just In my case it is broken, I hear cracks and dropouts with my Soundblaster Live card and the emu10k driver. It gets worse with higher loads and uptime. I experienced the same with onboard sound (VIA 8237/ALC850). I think these problems are well known since the first 5.x releases. doesn't work on your hardware (or you're using the wrong driver). You also forgot to describe your system. No, I didn't describe my system(s), because it wasn't my intention to ask for help or support with this mail. When you encounter a problem, as you apparently did, you need to inform the appropriate people (e.g. port maintainer), otherwise there's no way they can help you to resolve it. In this special case (devel/pear) we had a thread in ports@, and the maintainer was involved but obviously couldn't help with this problem, at least he did not comment on this. Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DLT Tape Read errors on aac0
Christian Gründemann wrote: Thanks for your fast answer, Scott! What Adaptec Card can you recommend? I am thinking about this card, it seems to be supported quite well. * Adaptec 19160B Is this card a real SCSI card ? Actually I thought the 2120S is a real SCSI Card. And for the future, what kind of Adaptec RAID-5 card is useable where I can put several devices on it like a Raid-5 *and* a DLT device ? Christian An Adaptec 19160 would be an excellent choice. By 'real SCSI card' I mean one that only does SCSI and doesn't have a RAID processor sitting in front on it. I don't have a good answer for your last question. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Schedule for 2006
On Sun, Dec 18, 2005 at 12:44:06PM -0800, Doug Barton wrote: regression in this area in RELENG_6, it would be worth reporting to this list, hopefully with enough detail that a developer could help you troubleshoot the problem. This problem already existed in 5.x, please have a look at kern/73744. Two things, first I seem to recall someone saying that the ral hardware is not all that hot to begin with, and you'd be better off with another wifi No, I don't use a ral card, in my case it's a Thinkpad with an iwi card. card. If that's not possible, have you tried upgrading to the latest 6-stable? If it's still not working after that, please report it to the Yes, I was always following RELENG_6 until 2 weeks ago when I finally installed Ubuntu on the Thinkpad, partly because of the wlan-problem, partly because FreeBSD does not boot with a second battery installed instead of the CD-/DVD-drive... list. Also, it's worth noting that if you're trying WPA on 5-stable, you're not likely to succeed. The infrastructure was greatly improved for 6-release. Yes, I know. the state that it is in right now (good or bad) because the community of its users helped make it that way. The only way it gets better is if people help make it better. Relying on them to do it for you is not the FreeBSD way. Yes, I know, although there were other statements recently (fix it or pay someone to fix it for you). tnx, Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: lockmgr: locking against myself
+-le 20/12/2005 01:13 +0800, Xin LI a dit : | Hi, Mathieu, | | On 12/20/05, Mathieu Arnold [EMAIL PROTECTED] wrote: | +-le 20/12/2005 00:00 +0800, Xin LI a dit : | | Hi, | | | | On 12/19/05, Mathieu Arnold [EMAIL PROTECTED] wrote: | | Unread portion of the kernel message buffer: | | panic: lockmgr: locking against myself | | | | Is it 6.0-RELEASE and you have mounted NFS? | | Both, yes. | | I think 6.0-RELEASE-p1 should have fixed it... You may want to | upgrade to RELENG_6_0 to get the patches. I saw the commit about that, I'll see :-) Thanks -- Mathieu Arnold pgpS5lzLIyJbi.pgp Description: PGP signature
Re: 6.0/amd64 boot hang if apic enabled on IBM x336
Would you tell me how to enable HTT? I've set 2 parameters hyperthreading_allowed=1 hlt_logical_cpus=0 but FreeBSD 6.0-RELEASE does not start logical CPU Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] On Mon, 19 Dec 2005, Joseph Koshy wrote: mk The question I have. Does Intel CPU have HTT in amd64 mode? Yes, AFAIK. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ 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: DLT Tape Read errors on aac0
IBM ServeRAID 6i in IBM xSeries 345 doesn't see tape drive on second LSI Logic MPT channel (6i is a Zero channel RAID Controller). There was trouble with setting DDS-4 streamer under SCO. Due to lack of information provided by SCO OperServer 5.0.5 FreeBSD (5.3 or so) was tried to see, which devices are detected. After installation of Adaptec 19160 streamer was seen by FreeBSD, then was configured under SCO. As far as I know it works perfectly now. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] On Mon, 19 Dec 2005, Scott Long wrote: Christian Gr?ndemann wrote: Thanks for your fast answer, Scott! What Adaptec Card can you recommend? I am thinking about this card, it seems to be supported quite well. * Adaptec 19160B Is this card a real SCSI card ? Actually I thought the 2120S is a real SCSI Card. And for the future, what kind of Adaptec RAID-5 card is useable where I can put several devices on it like a Raid-5 *and* a DLT device ? Christian An Adaptec 19160 would be an excellent choice. By 'real SCSI card' I mean one that only does SCSI and doesn't have a RAID processor sitting in front on it. I don't have a good answer for your last question. Scott ___ 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: DLT Tape Read errors on aac0
The ServeRAID/ips driver in FreeBSD cannot talk directly to the SCSI bus on the RAID card, nor does the card export non-RAID devices to the driver, nor do I know if there is a way to make this work. Seriously, using a $200-$1000 RAID card to run your tape drive in place of a $40 SCSI card really doesn't make a whole lot of sense in most cases. I understand that there are situations where there aren't enough PCI slots for an extra SCSI card, but it's a tradeoff. Most firmware simply isn't written to multiplex direct SCSI requests from the OS with it's own SCSi stack. Trying to do so only jeopardizes the integrity of the system. Scott Maxim M. Kazachek wrote: IBM ServeRAID 6i in IBM xSeries 345 doesn't see tape drive on second LSI Logic MPT channel (6i is a Zero channel RAID Controller). There was trouble with setting DDS-4 streamer under SCO. Due to lack of information provided by SCO OperServer 5.0.5 FreeBSD (5.3 or so) was tried to see, which devices are detected. After installation of Adaptec 19160 streamer was seen by FreeBSD, then was configured under SCO. As far as I know it works perfectly now. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] On Mon, 19 Dec 2005, Scott Long wrote: Christian Gr?ndemann wrote: Thanks for your fast answer, Scott! What Adaptec Card can you recommend? I am thinking about this card, it seems to be supported quite well. * Adaptec 19160B Is this card a real SCSI card ? Actually I thought the 2120S is a real SCSI Card. And for the future, what kind of Adaptec RAID-5 card is useable where I can put several devices on it like a Raid-5 *and* a DLT device ? Christian An Adaptec 19160 would be an excellent choice. By 'real SCSI card' I mean one that only does SCSI and doesn't have a RAID processor sitting in front on it. I don't have a good answer for your last question. Scott ___ 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]
Firefox/Thunderbird: Weired close behaviour (stuck) and installation problems
Hello. Since a few days I recognize a weired behaviour of both Mozilla Firefox 1.5 and Mozilla Thunderbird 1.0.7 on FreeBSD 6.0-STABLE/AMD64/i386: - when closing both applications, the close their window but there is still a process eating up CPU time with state 'ucond'. kill -9 # helps. As far as I can remember this misbehaviour wasn't obvious befor last week (I do cvsupdates on a two-daily cycle). On both, amd64 and i386, types of the most recent FreeBSD 6.0-STABLE, doing a portupgrade fails for thunderbird, I remains stuck on this last message forever: install -o root -g wheel -m 444 /usr/data/ports/usr/data/ports/mail/thunderbird/work/fake/libdata/pkgconfig/thunderbird-plugin.pc /usr/X11R6/libdata/pkgconfig/thunderbird-plugin.pc /bin/mkdir -p /usr/X11R6/lib/browser_plugins /usr/bin/touch -f /usr/X11R6/lib/browser_plugins/.thunderbird.keep === Building Chrome's registry... Can anyone confirm or help, in case this is a fault on my own weirdness? Thanks, Oliver P.S. I do not apply a dmesg because this error occurs on all diffrent flavours of hardware but with the same OS: FReeBSD 6.0-STABLE (most recent). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DLT Tape Read errors on aac0
On Tue, Dec 20, 2005 at 12:05:46AM +0600, Maxim M. Kazachek wrote: After installation of Adaptec 19160 streamer was seen by FreeBSD, then was configured under SCO. As far as I know it works perfectly now. I have a Seagate DDS-4 sa0 mounted off of an Adapted 29320 card, and that works fine. I have an Adaptec 2230SLP on the way, for use in an AMD-64 configuration, and from the sounds of things, I am doing the right thing in planning to either migrate the 29320 forward or using the on-board (LSI) SCSI of the new board. Bruce -- I like bad! Bruce BurdenAustin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic while messing with dhclient on 6.0-RELEASE
Using the Gnome applet for network interfaces, I checked DHCP for
interface em0. It sucessfully got an IP address. I then realized that
this would not be good (I use wireless at home with ath0), so I went
back and undid the changes in /etc/rc.conf. Then I tried running
'dhclient em0' again a few times from the command line (it seemed like
it was taking forever) and eventually got a panic:
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc04c6238
stack pointer = 0x28:0xd547cb60
frame pointer = 0x28:0xd547cb74
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 27 (swi1: net)
trap number = 12
panic: page fault
Uptime: 5m49s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 511MB (130656 pages) 495 479 463 447 431 415 399 383 367 351
335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47
31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc04a6432 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc04a66c8 in panic (fmt=0xc05befc2 %s)
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc05a8d30 in trap_fatal (frame=0xd547cb20, eva=36)
at /usr/src/sys/i386/i386/trap.c:831
#4 0xc05a8516 in trap (frame=
{tf_fs = -716767224, tf_es = -1068826584, tf_ds = -1049952216,
tf_edi = -1050872656, tf_esi = -1038145184, tf_ebp = -716715148, tf_isp
= -716715188, tf_ebx = -1067400680, tf_edx = 40, tf_ecx = 0, tf_eax = 0,
tf_trapno = 12, tf_err = 0, tf_eip = -1068735944, tf_cs = 32, tf_eflags
= 589958, tf_esp = 40, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:267
#5 0xc0598e7a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc04c6238 in propagate_priority (td=0xc21f2960)
at /usr/src/sys/kern/subr_turnstile.c:233
#7 0xc04c69e6 in turnstile_wait (lock=0xc16fa87c, owner=0xc1629640)
at /usr/src/sys/kern/subr_turnstile.c:628
#8 0xc049dc9c in _mtx_lock_sleep (m=0xc16fa87c, tid=3244094640, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:553
#9 0xc0516aa9 in rtalloc1 (dst=0xd547cc28, report=0, ignflags=0)
at /usr/src/sys/net/route.c:148
#10 0xc051b88d in arplookup (addr=0, create=0, proxy=0)
at /usr/src/sys/netinet/if_ether.c:913
#11 0xc051b1b9 in in_arpinput (m=0xc200)
at /usr/src/sys/netinet/if_ether.c:692
#12 0xc051af0e in arpintr (m=0xc200) at
/usr/src/sys/netinet/if_ether.c:553
#13 0xc0514183 in netisr_processqueue (ni=0xc060d9f8)
at /usr/src/sys/net/netisr.c:236
#14 0xc051437e in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:349
#15 0xc0492029 in ithread_loop (arg=0xc1585400)
at /usr/src/sys/kern/kern_intr.c:547
#16 0xc04912b0 in fork_exit (callout=0xc0491ed0 ithread_loop,
arg=0xc1585400, frame=0xd547cd38) at /usr/src/sys/kern/kern_fork.c:789
#17 0xc0598edc in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
(kgdb) frame 6
#6 0xc04c6238 in propagate_priority (td=0xc21f2960)
at /usr/src/sys/kern/subr_turnstile.c:233
233 ts = td-td_blocked;
(kgdb) list *0xc04c6238
0xc04c6238 is in propagate_priority
(/usr/src/sys/kern/subr_turnstile.c:235).
230 /*
231 * Pick up the lock that td is blocked on.
232 */
233 ts = td-td_blocked;
234 MPASS(ts != NULL);
235 tc = TC_LOOKUP(ts-ts_lockobj);
236 mtx_lock_spin(tc-tc_lock);
237
238 /* Resort td on the list if needed. */
239 if (!turnstile_adjust_thread(ts, td)) {
(kgdb) print td
$1 = (struct thread *) 0xc21f2960
(kgdb) print td-td_blocked
$2 = (struct turnstile *) 0x0
(kgdb)
This was on 6.0-RELEASE with a custom kernel. Mostly just have things
set up as modules instead of compiling them direclty into the kernel
(if_em is a module BTW). I hope I've captured all the relevant
information. If not, I've still got the dump, and can do further analysis.
Joel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i915drm
Gianmarco [EMAIL PROTECTED] wrote: I am running FreeBSD 6.0-STABLE (of today) on a HP Pavillon (centrino based notebook with i915 graphic chipset). Same here (Centrino, i915, not HP though). I am trying to use the latest drm hook for i915, but I get this error: drmsub0: Intel i915GM port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) Is there any mentioning of an AGP device (agp0) in your dmesg? If not, then that's probably the problem. It is interesting that your drmsub0 comes directly as a child of pci0. On my machine, it's a child of agp0. I get this in dmesg: agp0: Intel 82915GM (915GM GMCH) SVGA controller port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M drmsub0: Intel i915GM: (child of agp_i810.c) on agp0 info: [drm] AGP at 0xb008 0MB info: [drm] Initialized i915 1.2.0 20041217 pci0: display at device 2.1 (no driver attached) That's with RELENG_6 from yesterday (Dec. 18, 12:00 GMT). (By the way, it's normal that no driver is reported to be attached to device 2.1.) I'm using the latest Xorg development snapshot, which runs fine, including 2D acceleration, hardware cursor and XVideo extension with hardware acceleration (i.e. hardware scaler and color space conversion). No problems whatsoever. device agp # support several AGP chipsets device drm # DRM core module required by DRM drivers device i915drm # Intel i830 through i915 I have the same entries in my kernel config. and my pciconf -vl shows: [EMAIL PROTECTED]:2:0: class=0x03 card=0x3080103c chip=0x25928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS, 82910GML Integrated Graphics Device' class= display subclass = VGA [EMAIL PROTECTED]:2:1: class=0x038000 card=0x3080103c chip=0x27928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS,82910GML Mobile Express Family Graphics Controller (??)' class= display Just for comparison, this is mine: [EMAIL PROTECTED]:2:0: class=0x03 card=0xc01a144d chip=0x25928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS, 82910GML Integrated Graphics Device' class= display subclass = VGA [EMAIL PROTECTED]:2:1: class=0x038000 card=0xc01a144d chip=0x27928086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82915GM/GMS,82910GML Mobile Express Family Graphics Controller (??)' class= display Looks pretty much the same. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. I learned Java 3 years before Python. It was my language of choice. It took me two weekends with Python before I was more productive with it than with Java. -- Anthony Roberts ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: indefinite wait buffer: Does this indicate hardware issue?
** On Sat, 17 Dec 2005 00:49:48 +0800, Xin LI [EMAIL PROTECTED] said: Xin I have a box indicating the following sometimes: Xin swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096 We are having a very similar problem that we've been trying to diagnose off and on for a while. About 20% of the time the system will emit very similar messages. In each case processes trying to write to disks get stuck in the ufs state. This is a dual CPU AMD Athlon(tm) MP 1600+ system on a Tyan 2460 mobo with 512 MB of RAM and an ICP Vortex GDT8546RZ SATA RAID controller. Here is the result of a C-t on an interactive shell via a serial console: load: 0.00 cmd: csh 547 [ufs] 0.02u 0.01s 0% 2516k With the kernel debugger a few processes will be stuck in the same state: db ps pid proc uid ppid pgrp flag stat wmesgwchan cmd 647 c1a080000 645 647 110 [SLPQ ufs 0xc1856c08][SLP] cron 646 c18834182 644 646 110 [SLPQ biord 0xcbcff650][SLP] cron 645 c1a0a8300 493 493 000 [SLPQ ppwait 0xc1a0a830][SLP] cron 644 c1887c480 493 493 000 [SLPQ ppwait 0xc1887c48][SLP] cron 643 c1a0a4180 632 642 0004002 [SLPQ wdrain 0xc06a26c4][SLP] bsdtar 632 c1a08a3c0 631 632 0004002 [SLPQ pause 0xc1a08a70][SLP] tcsh 631 c1834624 1001 616 631 0004102 [SLPQ wait 0xc1834624][SLP] su 616 c188720c 1001 615 616 0004002 [SLPQ pause 0xc1887240][SLP] tcsh 615 c1a0a624 1001 613 613 100 [SLPQ select 0xc06a2144][SLP] sshd 613 c18836240 471 613 0004100 [SLPQ sbwait 0xc1b3dbc8][SLP] sshd 547 c1671a3c0 537 547 0004002 [SLPQ ufs 0xc1856c08][SLP] csh 537 c1883a3c0 1 537 0004102 [SLPQ wait 0xc1883a3c][SLP] login 536 c18876240 1 536 0004002 [SLPQ ttyin 0xc16e8810][SLP] getty 535 c16716240 1 535 0004002 [SLPQ ttyin 0xc16e8410][SLP] getty 534 c1a0aa3c0 1 534 0004002 [SLPQ ttyin 0xc16dac10][SLP] getty 533 c1671c480 1 533 0004002 [SLPQ ttyin 0xc16e7010][SLP] getty 532 c1a0ac480 1 532 0004002 [SLPQ ttyin 0xc16e7410][SLP] getty 531 c1887a3c0 1 531 0004002 [SLPQ ttyin 0xc16e7810][SLP] getty 530 c18870000 1 530 0004002 [SLPQ ttyin 0xc16e7c10][SLP] getty 529 c183420c0 1 529 0004002 [SLPQ ttyin 0xc16e8010][SLP] getty 513 c1a0a20c0 1 513 000 [SLPQ select 0xc06a2144][SLP] inetd 493 c1a088300 1 493 000 [SLPQ ufs 0xc1856c08][SLP] cron 481 c1883c48 25 1 481 100 [SLPQ pause 0xc1883c7c][SLP] sendmail 477 c167120c0 1 477 100 [SLPQ pause 0xc1671240][SLP] sendmail 471 c18340000 1 471 100 [SLPQ select 0xc06a2144][SLP] sshd 349 c18874180 1 349 000 [SLPQ ufs 0xc1856c08][SLP] ypbind 336 c18344180 1 336 000 [SLPQ select 0xc06a2144][SLP] rpcbind 317 c18878300 1 317 000 [SLPQ select 0xc06a2144][SLP] syslogd 283 c16718300 1 283 000 [SLPQ select 0xc06a2144][SLP] devd 228 c1883000 65 1 228 100 [SLPQ select 0xc06a2144][SLP] dhclient 208 c188320c0 153 002 [SLPQ select 0xc06a2144][SLP] dhclient 52 c1834a3c0 0 0 204 [SLPQ - 0xd5526d08][SLP] schedcpu 51 c1834c480 0 0 204 [SLPQ - 0xc06aa4cc][SLP] nfsiod 3 50 c161b6240 0 0 204 [SLPQ - 0xc06aa4c8][SLP] nfsiod 2 49 c161b8300 0 0 204 [SLPQ - 0xc06aa4c4][SLP] nfsiod 1 48 c161ba3c0 0 0 204 [SLPQ - 0xc06aa4c0][SLP] nfsiod 0 47 c161bc480 0 0 204 [SLPQ vlruwt 0xc161bc48][SLP] vnlru 46 c1670 0 0 204 [SLPQ getblk 0xcbc36578][SLP] syncer 45 c167020c0 0 0 204 [SLPQ psleep 0xc06a268c][SLP] bufdaemon 44 c16704180 0 0 20c [SLPQ pgzero 0xc06b09c4][SLP] pagezero 9 c16706240 0 0 204 [SLPQ psleep 0xc06b0514][SLP] vmdaemon 8 c16708300 0 0 204 [SLPQ psleep 0xc06b04d0][SLP] pagedaemon 43 c1670a3c0 0 0 204 [IWAIT] swi0: sio 7 c1670c480 0 0 204 [SLPQ - 0xc16dd43c][SLP] fdc0 6 c16710000 0 0 204 [SLPQ - 0xc166f280][SLP] kqueue taskq 42 c160fc480 0 0 204 [IWAIT] swi5:+ 5 c161a0000 0 0 204 [SLPQ - 0xc15c1280][SLP] thread taskq 41 c161a20c0 0 0 204 [IWAIT] swi6:+ 40 c161a4180 0 0 204 [IWAIT] swi6: task queue 39 c161a6240 0 0 204 [IWAIT] swi2: cambio 38 c161a8300 0 0 204 [SLPQ - 0xc0698140][SLP] yarrow 4 c161aa3c0 0 0 204 [SLPQ - 0xc0698b08][SLP] g_down 3 c161ac480 0 0 204 [SLPQ - 0xc0698b04][SLP] g_up 2 c161b0000 0 0 204 [SLPQ - 0xc0698afc][SLP] g_event 37 c161b20c0 0 0 204 [IWAIT] swi3: vm 36 c161b4180 0 0 20c [IWAIT] swi4: clock sio 35 c16006240 0 0 204
Re: i915drm
Patrick Lamaizière [EMAIL PROTECTED] wrote: But dri does not work, Xorg seems to look for a /dev/dri/card0 and i've got only one device /dev/dri/card1 ? Xorg.log: (II) I810(0): Allocated 64 kB for the scratch buffer at 0x7fee000 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module i915 Strange. It works fine for me: (II) I810(0): Allocated 64 kB for the scratch buffer at 0xffee000 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: Searching for BusID pci::00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 9, (OK) drmOpenByBusid: drmOpenMinor returns 9 drmOpenByBusid: drmGetBusid reports pci::00:02.0 (II) I810(0): [drm] DRM interface version 1.2 (II) I810(0): [drm] created i915 driver at busid pci::00:02.0 (II) I810(0): [drm] added 8192 byte SAREA at 0xc5307000 (II) I810(0): [drm] mapped SAREA 0xc5307000 to 0x28744000 (II) I810(0): [drm] framebuffer handle = 0xc002 (II) I810(0): [drm] added 1 reserved context for kernel .. etc. ... Are you sure that you're using the latest RELENG_6 _and_ the latest Xorg development snapshot? You need both for things to work correctly. (I'm not using DRM/DRI, because I'm not playing games on my notebook, and I don't need 3D OpenGL screen savers either, but according to the logs and everything, it is detected and initialized correctly. However, I am using the XVideo extension for full-screen video playback with hardware acceleration, and that requires the presence of DRM, too -- that's why I configured it in my kernel.) Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly. -- RFC 2549 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0-R random freezes
Hi! I have machine running OpenBSD without any problems. When I put FreeBSD 6.0-R to this machine it started randomly freezing with and without load. It does not respond to keyboard ctrl-alt-esc, ctrl-alt-del (with KDB in kernel) and by network. So I rebuild kernel with DDB, attached serial console, and send break with minicom when it freezed. KD@: enter: Line break on console [thread pid 22 tid 100011 ] Stopped at kdb_enter+0x2b: nop db where Tracing pid 22 tid 100011 td 0xc0d91300 kdb_enter(c064968f) at kdb_enter+0x2b siointr1(c0e4f800) at siointr1+0xce siointr(c0e4f800) at siointr+0x38 intr_execute_handlers(c067c140,c5a38c7c,c9f38068,c0e33400,6) at intr_execute_ha5 atpic_handle_intr(4) at atpic_handle_intr+0x96 Xatpic_intr4() at Xatpic_intr4+0x20 --- interrupt, eip = 0xc0484d03, esp = 0xc5a38cc0, ebp = 0xc5a38cd4 --- lnc_tint(c0e33400) at lnc_tint+0x47 lncintr(c0e33400) at lncintr+0xf7 ithread_loop(c0d89680,c5a38d38) at ithread_loop+0x159 fork_exit(c04dd348,c0d89680,c5a38d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc5a38d6c, ebp = 0 --- db show lockedvnods Locked vnodes db ps pid proc uid ppid pgrp flag stat wmesgwchan cmd 695 c104fc480 692 695 0004002 [SLPQ ttyin 0xc0e4fc10][SLP] bash 692 c0ec5418 10641 691 692 0004002 [SLPQ wait 0xc0ec5418][SLP] bash 691 c104f20c0 1 691 0004102 [SLPQ wait 0xc104f20c][SLP] login 475 c0f84c48 100 435 475 0004000 [SLPQ piperd 0xc0ef2330][SLP] unlinkd 474 c0f8420c0 1 1 0004000 [SLPQ nanslp 0xc068752c][SLP] getty 472 c0f844180 1 472 0004002 [SLPQ ttyin 0xc0e57010][SLP][SWAP] getty 471 c0f840000 1 471 0004002 [SLPQ ttyin 0xc0e56010][SLP][QWAP] getty 470 c0f846240 1 470 0004002 [SLPQ ttyin 0xc0e55c10][SLP][SWAP] getty 435 c0ec6624 100 433 433 0004000 [SLPQ select 0xc068bf64][SLP] squid 433 c0ec620c 100 1 433 000 [SLPQ wait 0xc0ec620c][SLP][SWAP] squid 432 c0ec6c48 1100 418 432 0004002 [SLPQ select 0xc068bf64][SLP] mlnet-real 418 c0ec68300 143 0004102 [SLPQ wait 0xc0ec6830][SLP][SWAP] su 398 c0e138300 1 398 000 [SLPQ nanslp 0xc068752c][SLP] cron 385 c0e136240 1 385 100 [SLPQ select 0xc068bf64][SLP] sshd 242 c0e13a3c0 1 242 000 [SLPQ select 0xc068bf64][SLP][SWAP] devd 151 c0ec520c0 1 151 000 [SLPQ pause 0xc0ec5240][SLP][SWAP] adjkz 42 c0ec58300 0 0 204 [SLPQ - 0xc5e85d08][SLP] schedcpu 41 c0ec5a3c0 0 0 204 [SLPQ syncer 0xc068729c][SLP] syncer 40 c0ec5c480 0 0 204 [SLPQ vlruwt 0xc0ec5c48][SLP] vnlru 39 c0ec60000 0 0 204 [SLPQ psleep 0xc068c4ac][SLP] bufdaemon 38 c0db4c480 0 0 20c [SLPQ pgzero 0xc068fc24][SLP] pagezero 37 c0e120000 0 0 204 [SLPQ psleep 0xc068f774][SLP] vmdaemon 36 c0e1220c0 0 0 204 [SLPQ psleep 0xc068f730][SLP] pagedaemon 35 c0e124180 0 0 204 [IWAIT] swi0: sio 34 c0e126240 0 0 204 [SLPQ - 0xc0d8203c][SLP] fdc0 9 c0e128300 0 0 204 [SLPQ - 0xc0e20400][SLP] thread taskq 33 c0e12a3c0 0 0 204 [IWAIT] swi6:+ 32 c0e12c480 0 0 204 [IWAIT] swi6: task queue 8 c0e130000 0 0 204 [SLPQ - 0xc0d8a480][SLP] acpi_task2 7 c0e1320c0 0 0 204 [SLPQ - 0xc0d8a480][SLP] acpi_task1 6 c0e134180 0 0 204 [SLPQ - 0xc0d8a480][SLP] acpi_task0 5 c0da56240 0 0 204 [SLPQ - 0xc0d8a580][SLP] kqueue taskq 31 c0da58300 0 0 204 [IWAIT] swi5:+ 30 c0da5a3c0 0 0 204 [SLPQ - 0xc0683fe0][SLP] yarrow 4 c0da5c480 0 0 204 [SLPQ - 0xc0684a48][SLP] g_down 3 c0db40000 0 0 204 [SLPQ - 0xc0684a44][SLP] g_up 2 c0db420c0 0 0 204 [SLPQ - 0xc0684a3c][SLP] g_event 28 c0db46240 0 0 204 [IWAIT] swi3: vmt 27 c0db48300 0 0 20c [RUNQ] swi4: clock sio 25 c0d9020c0 0 0 204 [IWAIT] irq14: ata0 24 c0d904180 0 0 204 [IWAIT] irq13: 23 c0d906240 0 0 204 [IWAIT] irq12: 22 c0d908300 0 0 204 [APU 0] irq11: lnc0 21 c0d90a3c0 0 0 204 [IWAIT] irq10: 20 c0d90c480 0 0 204 [IWAIT] irq9: acpi0 19 c0da50000 0 0 204 [IWAIT] irq8: rtc 18 c0da520c0 0 0 204 [IWAIT] irq7: ppc0 17 c0da54180 0 0 204 [IWAIT] irq6: fdc0 16 c0d8b0000 0 0 204 [IWAIT] irq5: 15 c0d8b20c0 0 0 204 [IWAIT] irq4: sio0 14 c0d8b4180 0 0 204 [IWAIT] irq3: 13 c0d8b6240 0 0 204 [IWAIT] irq1: atkbd0 12 c0d8b8300 0 0 204 [IWAIT] irq0: clk 11 c0d8ba3c0 0 0 20c [Aan run] idle 1 c0d8bc480 0
Cx states missing after upgrade -- Was: Re: HEADS UP: Release schedule for 2006
Kevin Oberman wrote: Date: Sun, 18 Dec 2005 20:46:49 +0100 From: martinko [EMAIL PROTECTED] Kevin Oberman wrote: Date: Sat, 17 Dec 2005 18:14:01 +0100 From: martinko [EMAIL PROTECTED] Kevin Oberman wrote: Date: Fri, 16 Dec 2005 14:29:39 -0600 From: Craig Boston [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] -cpu0: ACPI CPU (4 Cx states) on acpi0 +cpu0: ACPI CPU on acpi0 Q: Guessing that's a formatting difference, rather then 6.x not recognizing the states (sysctl hw.acpi.cpu.cx_supported confirms 4 states) Not sure on this, but you're probably better off using EST anyway as I think it gives you more control over the processor frequency. No. There is no conflict between Cx states and EST. Cx states specifies how deeply the CPU will sleep when idle. EST controls processor speed and voltage. In most cases, your REALLY want to use both of these. They are very significant in saving power. (Of course, USB tends to limit the effectiveness of Cx states. I need to run without USB to get really good battery life and to make suspend (S3) really ut power drain. Kevin, I used to have 3 Cx states supported when I started with FreeBSD on version 5.3. Since I upgraded to 5.4 and recently to 6.0, all I can see is just one supported Cx state. I much wonder why. (?) What value do you have in /etc/rc.conf (if any) for performance_cx_lowest? It defaults to HIGH which will limit you to only the most power hungry sleep state (simple halt). This was made the default because some hardware was breaking when this was defaulted to LOW. T0 get other Cx states to be utilized, add 'performance_cx_lowest=LOW' to /etc/rc.conf. i see. anyway: # grep cx /etc/rc.conf.local economy_cx_lowest=LOW performance_cx_lowest=LOW still: # sysctl hw.acpi.cpu hw.acpi.cpu.cx_supported: C1/1 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% and, imho, cx_supported should list all available states, doesn't matter what is in rc.conf. (well, at least i reckon it's supposed to work that way.) but: i already had 3 Cx states back on 5.3. and when i had them, C2 was used most often (and C3 wasn't at all iirc). so what has changed in the system please and how am i to get back my states please ?? This is a totally different problem. I thought that the problem was simply not using all of the states. Instead, you are not even showing the states as available. Looks like the kernel is not reading the capabilities of your system correctly. This seems to coincide with the new ACPI code import. Sounds like something is not being handled properly and it is likely beyond my capability to track it down. I would suggest posting your the output of 'acpidump -t -d' on a web site and then sending a report with a pointer to that ASL to [EMAIL PROTECTED] There it will be seen by the folks who really know the ACPI stuff. hello! thank you, kevin. i did as you advised and here are the outputs of acpidump: # acpidump -t -d -o asus_w1n.dsdt asus_w1n.asl acpidump: RSDT entry 1 (sig OEMB) is corrupt http://mato.gamato.org/freebsd/aw1n/asus_w1n.dsdt http://mato.gamato.org/freebsd/aw1n/asus_w1n.asl i look forward to hearing from you folks.. :-) many thanks! regards, martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i915drm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Fromme wrote: Gianmarco [EMAIL PROTECTED] wrote: I am running FreeBSD 6.0-STABLE (of today) on a HP Pavillon (centrino based notebook with i915 graphic chipset). Same here (Centrino, i915, not HP though). I am trying to use the latest drm hook for i915, but I get this error: drmsub0: Intel i915GM port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) Is there any mentioning of an AGP device (agp0) in your dmesg? If not, then that's probably the problem. It is interesting that your drmsub0 comes directly as a child of pci0. On my machine, it's a child of agp0. I get this in dmesg: agp0: Intel 82915GM (915GM GMCH) SVGA controller port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M drmsub0: Intel i915GM: (child of agp_i810.c) on agp0 info: [drm] AGP at 0xb008 0MB info: [drm] Initialized i915 1.2.0 20041217 pci0: display at device 2.1 (no driver attached) In my HP Compaq nx6110 (i915GM) too drmsub wants to come directly as a child of pci0: drmsub0: Intel i915GM port 0x7000-0x7007 mem 0xd040-0xd047,0xc000-0xcfff,0xd048-0xd04b irq 16 at device 2.0 on pci0 [drm:pid0:drm_load] [drm:pid0:drm_agp_init] agp_available = 0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. [drm:pid0:drm_lastclose] device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) If I have drm loaded after boot time (by X.org) there will be agpgart but no dri/cardX... Best, Laci - -- László Károly [EMAIL PROTECTED] Department of Altaic StudiesEgyetem str. 2. University of Szeged H-6722 Szeged, Hungary PGP/GnuPG key: 1024D/869D81C5 Fingerprint: 1E61 3205 8F5A 87E7 1269 3396 1C63 F9FF 869D 81C5 Encrypted e-mail preferred. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDp026HGP5/4adgcURAt33AJ9GrO4sLJEMWguEqK/4JqaRWPXO/wCglKHu Txo1xArRPtpJMGeO0jLTKII= =6NZN -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Request Requeued/Retrying Command with twa card on FreeBSD 6.0
I've got a weird but apparently minor issue with a 3Ware 9500S-4LP in a FreeBSD 6.0-RELEASE system... When the system is run with boot.verbose=YES in /boot/loader.conf, I get these messages on the console: (da0:twa0:0:0:0): Request Requeued (da0:twa0:0:0:0): Retrying Command (da0:twa0:0:0:0): Request Requeued (da0:twa0:0:0:0): Retrying Command (repeat a few dozen times each time) ...during some heavy disk activity, like, for example, qpopper rewriting a 50 MB mailbox. (I know qpopper's a bit of a slug.) Not all heavy disk IO triggers it, though; I can do something like dd if=/dev/zero of=/tmp/testfile bs=10485760 count=128 followed by dd if=/tmp/testfile of=/dev/null bs=10485760 and have it complete without a single SCSI timeout message. Turn boot.verbose=NO off and the messages go away, but IO still lags badly. camcontrol tags says it has 254 tag openings, which seems like a bit much. Dropping down to 16 seems to make the messages go away. Do the twa cards even do TCQ between the card and the OS? From what I understand, they won't do NCQ between the card and the SATA disks, even if you have something like Barracudas that support it -- you need the new 3Ware 9550 card for that. If they don't, why does it advertise 254 tags, and if it does, why does it seem to choke on the default setting of 254? Other than laggy IO (shell prompts hang, MP3's skip for 5 - 30 seconds) there aren't any actual IO errors or anything else wrong, which for this particular system is just minor annoyance instead of serious problem. 5.4-RELEASE did the same thing. I have an apparent workaround, I'm just trying to sanity-check it and its necessity. This is an Asus P4C800-E Deluxe board, so I'm running the twa card in a 32-bit slot. The system is otherwise totally idle when this happens, no interrupt storms, USB and Firewire disabled in the BIOS so we don't have IRQs shared with Giant-locked drivers... dmesg, vmstat -i, other stuff available on request if needed. Kernel config is the stock 'SMP' one. Mike Andrews * [EMAIL PROTECTED] * http://www.bit0.com It's not news, it's Fark.com. Carpe cavy! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0/amd64 boot hang if apic enabled on IBM x336
mk The question I have. Does Intel CPU have HTT in amd64 mk mode? jk Yes, AFAIK. mk Would you tell me how to enable HTT? mk I've set 2 parameters mk hyperthreading_allowed=1 mk hlt_logical_cpus=0 mk but FreeBSD 6.0-RELEASE does not start logical CPU Please check if your CPU supports multiple HTT logical CPUs in the first place. If it does, your dmesg output should be something like the snippet below: CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz K8-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x20100800SYSCALL,NX,LM Hyperthreading: 2 logical CPUs ... FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ports security branch
Is there a security branch for the FreeBSD ports collection? Let's say, I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages (i.e., those on the CD). Running security/portaudit after a while reveals that some of the installed packages have vulnerabilities. Am I on my own to go grab the fresh ports tree, and upgrade the affected software, suffering all the intricacies of the move by myself? Debian GNU/Linux has its security package updates, OpenBSD has a separately maintained errata ports branch (it's very likely you still get to download a newer release of the software, though). Sorry if this is a bit OT. I've already asked this on freebsd-questions@ but they told me there's no such thing at all. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i915drm
Hi. László Károly wrote: drmsub0: Intel i915GM port 0x1800-0x1807 mem 0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16 at device 2.0 on pci0 error: [drm:pid0:drm_load] *ERROR* Card isn't AGP, or couldn't initialize AGP. device_attach: drmsub0 attach returned 12 pci0: display at device 2.1 (no driver attached) i915 DRM is not fully supported in -stable. You may try 7-current or this hack: ftp://213.85.11.250/pub/drm3.patch . With best regards, Alexey Popov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ports security branch
On Tuesday, December 20, 2005 6:26 AM when we last met our heroes, [EMAIL PROTECTED] was heard to say: Sorry if this is a bit OT. I've already asked this on freebsd-questions@ but they told me there's no such thing at all. And they were correct. The overhead of managing such a thing correctly would be significant, probably more than the overhead of managing the base port itself. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
