Re: problem with iwi driver in 8.0 and custom kernel (works on generic)
(i've tried to compile kernel with/without optimizations which you will find commented out in the configuration attached to the mail, obtaining always the same interrupt storm problem.) forgot to attach the configuration, sorry :) regards ocean # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 kensmith Exp $ cpu I686_CPU ident mykernel # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env "GENERIC.env" #makeoptions COPTFLAGS="-O2 -pipe -funroll-loops -fno-strict-aliasing -ffast-math" #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking #optionsINET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFSLOCKD# Network Lock Manager #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache #optionsKDTRACE_HOOKS # Kernel DTrace hooks # To make an SMP kernel, the next two lines are needed #optionsSMP # Symmetric MultiProcessor Kernel #device apic# I/O APIC # CPU frequency control device cpufreq # Bus support. device acpi device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID dr
Re: Disc lock up on 8.0-STABLE
Just to report that the machine didn't crash last night - which doesn't make me happy as it makes me think maybe I am chasing the wrong thing! I now have DDB and KDb in the kernel now, will get traces next tme it keels over. -pete. ___ 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 8.0: can't PXE Boot using nvidia nForce4 network card
Hi all, I've got a PC which have 2 bugs with FreeBSD 8.0: It can't boot from USB (usb/139142) neither from PATA hard-drive (kern/139143). But I would boot this PC for giving acces to somes FreeBSD devs for debuging it: Then I've choose boot my buggy PC using PXE, then I've prepared a second PC with a DHCP/TFTP/NFS/serial-cable this bugguy PC. I've posted my problem on the FreeBSD forum some weeks ago, but didn't found usefull help: http://forums.freebsd.org/showthread.php?t=8324 The up-to-date 8.0-STABLE kernel boot fine from PXE/TFTP, but when it tries to mount the rootfilesystem from NFS it display an errror: Trying to mount root from nfs:10.0.0.1:/usr/tftpboot nfs_diskless: no interface ROOT MOUNT ERROR: The network card is a NVIDIA nForce4 CK804 MCP8. I've seen that the pxe loader populate correctly lot's of the needed boot variables (boot.netif.ip, boot.netif.netmask, boot.netif.gateway, etc...) but with the only expection of "boot.netif.name". It seems to have a problem in /usr/src/sys/nfsclient/nfs_diskless.c that can't set this variable. Does some one have any clue for fixing this file ? Thanks, Olivier PS: Here is the full verbose boot messages: SMAP type=01 base= len=0009f800 SMAP type=02 base=000f len=0001 SMAP type=02 base=fec0 len=1000 SMAP type=02 base=fee0 len=0010 SMAP type=02 base=fefffc00 len=0400 SMAP type=02 base= len=0001 SMAP type=02 base=e000 len=1000 SMAP type=03 base=7fff3000 len=d000 SMAP type=04 base=7fff len=3000 SMAP type=02 base=0009f800 len=0800 SMAP type=01 base=0010 len=7fef 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 8.0-STABLE #3: Wed Dec 23 01:14:48 CET 2009 r...@debugger.bsdrp.net:/usr/obj/usr/src/sys/GENERIC i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0f79000. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2010313531 Hz CPU: AMD Athlon(tm) 64 Processor 3000+ (2010.31-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 Data TLB: 32 entries, fully associative Instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative WARNING: This architecture revision has known SMP hardware bugs which may cause random instability real memory = 2147483648 (2048 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x01026000 - 0x7db9afff, 2092388352 bytes (510837 pages) avail memory = 2091081728 (1994 MB) Table 'FACP' at 0x7fff30c0 Table 'MCFG' at 0x7fff96c0 Table 'APIC' at 0x7fff9600 APIC: Found table at 0x7fff9600 MP Configuration Table version 1.4 found at 0xc00f1400 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) ACPI APIC Table: APIC: CPU 0 has ACPI ID 0 bios32: Found BIOS32 Service Directory header at 0xc00fb950 bios32: Entry = 0xf1f80 (c00f1f80) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x1fb0 pnpbios: Found PnP BIOS data at 0xc00fc4d0 pnpbios: Entry = f:c500 Rev = 1.0 Other BIOS signatures found: ULE: setup cpu 0 ACPI: RSDP 0xf77b0 00014 (v0 Nvidia) ACPI: RSDT 0x7fff3040 00030 (v1 Nvidia AWRDACPI 42302E31 AWRD ) ACPI: FACP 0x7fff30c0 00074 (v1 Nvidia AWRDACPI 42302E31 AWRD ) ACPI: DSDT 0x7fff3180 06402 (v1 NVIDIA AWRDACPI 1000 MSFT 010E) ACPI: FACS 0x7fff 00040 ACPI: MCFG 0x7fff96c0 0003C (v1 Nvidia AWRDACPI 42302E31 AWRD ) ACPI: APIC 0x7fff9600 0006E (v1 Nvidia AWRDACPI 42302E31 AWRD ) MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level MADT: Interrupt override: source 14, irq 14 MADT: Interrupt override: source 15, irq 15 lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x VER: 0x00050010 LDR: 0x DFR: 0x lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff timer: 0x000100ef therm: 0x0001 err: 0x0001 pcm: 0x00010400 wlan: <802.11 Link Layer> null: random: nfslock: p
Re: Create socket files
Hi All The problem did seem to be that the service was not running as root as Adam suggested. I had this in rc.conf below. I'm assuming the second line runs the service as user daemon!? when I removed it, the service started. Thanks for the help. syslog_ng_enable="YES" syslog_ng_config="-u daemon" syslog_ng_pid="/var/run/syslog-ng.pid" On Tue, Dec 22, 2009 at 9:15 PM, Glen Barber wrote: > Hi Peter > > On Tue, Dec 22, 2009 at 8:34 PM, Peter Fraser wrote: >> Hi All >> I wonder if anyone could help me with this problem. I followed the >> instructions in the handbook to create some jails. It makes part of >> the filesystem readonly which is good. > > This sounds like you used the "service jail" approach [1]. Correct me > if I am wrong. > >> Problem is though that I tried >> installing syslog-ng in one of the jails and when I tried to start it, >> I got this error >> >>> Error binding socket; addr='AF_UNIX(/var/run/log)', error='Permission >>> denied (13)' >>> Error initializing source driver; source='src', id='src#0' >>> Error initializing message pipeline; >>> /usr/local/etc/rc.d/syslog-ng: WARNING: failed to start syslog_ng >> >> I think it's trying to create the socket files /var/run/log and >> /var/run/logpriv but can't. Is there anyway for me to create them >> manually? > > It has been some time since I used that method to create jails; the > areas that have burned me in particular were symlinking > /usr/local/bin/perl to /usr/bin/perl and similarly for the > security/ca_root_nss port. > > Re-reading the doc, /var should be made read/write as it is part of > the jail "skeleton" filesystem, from which you create the "moving > parts" of your jail, so to speak. Did you create /var read-only? > > Regards, > > > [1] - > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-application.html > > -- > Glen Barber > ___ 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"
Should not usbdevs be removed by "make delete-old" on 8-STABLE?
Hi # uname -a FreeBSD avatar 8.0-STABLE FreeBSD 8.0-STABLE #2: Wed Dec 23 13:41:06 BRST 2009 r...@avatar:/usr/obj/usr/src/sys/Compaq_nx6320 amd64 # ls -l /usr/sbin/usbdevs -r-xr-xr-x 1 root wheel 8320 27 Jan 2009 /usr/sbin/usbdevs Is there any reason to keep usbdevs installed now that 8.X uses the new USB stack? ___ 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"
smartmontools now works for new AHCI/ATA_CAM "ada" devices
Hi, FYI, I have just committed the update submitted by Alex Samorukov, per marck@'s approval. The most important change in this version is to support the new AHCI and ATA_CAM devices! Thanks everyone who made this happen! Original Message Subject: cvs commit: ports/sysutils/smartmontools Makefile distinfo ports/sysutils/smartmontools/files patch-knowndrives.cpp patch-os__freebsd.cpp patch-scsiata.cpp Date: Wed, 23 Dec 2009 18:55:52 + (UTC) From: Xin LI To: ports-committ...@freebsd.org, cvs-po...@freebsd.org, cvs-...@freebsd.org delphij 2009-12-23 18:55:52 UTC FreeBSD ports repository Modified files: sysutils/smartmontools Makefile distinfo Removed files: sysutils/smartmontools/files patch-knowndrives.cpp patch-os__freebsd.cpp patch-scsiata.cpp Log: Update to 5.39. This version is long awaited and the important improvements related to FreeBSD are: - USB device type autodetection for some devices http://sourceforge.net/apps/trac/smartmontools/wiki/Supported_USB-Devices - Support for HighPoint RocketRAID controllers - Support RAID controllers using /dev/pass devices - Support CHECK_POWER_MODE and WRITE_LOG - Fix CCISS file descriptor leak - New device type detection algorithm on FreeBSD, not based on filename - Support for the adaX (ATA on CAM bus) devices on FreeBSD 8.0 and higher PR: ports/141371 Submitted by: Alex Samorukov Approved by:marck (maintainer) Revision ChangesPath 1.45 +3 -2 ports/sysutils/smartmontools/Makefile 1.12 +3 -3 ports/sysutils/smartmontools/distinfo 1.3 +0 -11 ports/sysutils/smartmontools/files/patch-knowndrives.cpp (dead) 1.6 +0 -58 ports/sysutils/smartmontools/files/patch-os__freebsd.cpp (dead) 1.2 +0 -22 ports/sysutils/smartmontools/files/patch-scsiata.cpp (dead) ___ 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"
Follow-up on Teltonika ModemPCI/G10
Hi Guys! I guess I have just answered the question myself. I decided to buy the modem and try it. Guys in Teltonika told me that they haven't done any FreeBSD testing since they have nobody to do this. But they have sent me pdf with instruction how to setup the modem on Linux. The modem is working, but it required a bit of a work :-). I added few lines into /usr/src/sys/dev/puc/pucdata.c and recompiled kernel with the following additional configuration lines after that: device puc options COM_MULTIPORT After reboot I had two new serial ports cuau0 and cuau1 and was able to send an SMS message to my mobile phone. The question is how would I go about submitting the lines to developers, so they can review and hopefully commit it? :-) I have posted details of how I made it work to my wiki http://markelov.org/wiki/index.php/Teltonika_ModemPCI/G10_under_FreeBSD Hope it may help someone. Regards, Alex. ___ 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: Follow-up on Teltonika ModemPCI/G10
On 12/23/09, Alex Markelov wrote: > Hi Guys! > > I guess I have just answered the question myself. I decided to buy the > modem and try it. Guys in Teltonika told me that they haven't done any > FreeBSD testing since they have nobody to do this. But they have sent me pdf > with instruction how to setup the modem on Linux. > > The modem is working, but it required a bit of a work :-). I added few > lines into /usr/src/sys/dev/puc/pucdata.c and recompiled kernel with the > following additional configuration lines after that: > > device puc > options COM_MULTIPORT > > After reboot I had two new serial ports cuau0 and cuau1 and was able to > send an SMS message to my mobile phone. > > The question is how would I go about submitting the lines to developers, so > they can review and hopefully commit it? :-) > Create a diff between the original pucdata.c and your modified version, and then submit the patch file using either the web send-pr (http://www.freebsd.org/send-pr.html) or the send-pr command (send-pr -a pucdata.c-diff). Scot ___ 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"
