Re: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?
On Wed, 23 Dec 2009, Torfinn Ingolfsen wrote:
> On Mon, 21 Dec 2009 15:29:54 +1100 (EST)
> Ian Smith wrote:
>
> > Why is it booting up at half speed? Same in your 7.2-STABLE dmesg.
>
> I don't know. Since last time, I've upgraded the bios to the latest
> (A03) and reset bios to default values - but the problem is still there.
> According to the specs, a SX260 supports all Pentium 4 cpus with 400
> MHz and 533 MHz FSB (front side bus).
Yes, this is your problem, regarding speed anyway. I only picked up on
this because this year we bought 2 used intel mobos on eBay; a D845GBV
with a 2GHz P4 (also 400/533 MHz FSB with similar 845 chips to yours)
and the other a D865GLC with a 2.6GHz HTT P4 (400/533/800 MHz FSB).
Only the D865GLC 800MHz FSB board takes the 2.6GHz HTT P4, shown as
'2.60C GHz' in the board manual and also on this page:
http://www.intel.com/support/processors/pentium4/sb/CS-011987.htm
Our older 400/533 FSB board only takes a non-HTT P4 using 400MHZ FSB,
('2.60 GHz' without the 'C'), though it only has a 2GHz non-HTT CPU.
After a looong time hunting through fluff and bumph from various angles
and searches on the intel site (argh!), I finally found:
http://processorfinder.intel.com/List.aspx?ProcFam=483
Where there are several 478-pin 2.60GHz P4s with 512MB L2 cache, eg:
http://processorfinder.intel.com/details.aspx?sSpec=SL6WS (800MHz FSB)
http://processorfinder.intel.com/details.aspx?sSpec=SL6QR (400MHz FSB)
but all of the HTT 2.6GHz ones require 800MHz FSB, so I guess this is
why its set to run at half speed by your board? Perhaps the SX270 you
mentioned having taken this CPU out of, supported up to 800MHz FSB?
> > Something set that way in BIOS? What does 'sysctl dev.cpu' say?
>
> The only setting in bios related to cpu speed are
> "normal" and "comaptible". I've tried both - doesn't make a difference.
>
> Now sysctl.dev.cpu says:
> r...@kg-work2# sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 1295
> dev.cpu.0.freq_levels: 1295/-1 1133/-1 971/-1 809/-1 647/-1 485/-1 323/-1
Yeah, just p4tcc thermal throttling, no EST speedstep control on these;
powerd could save you some heat but not much less power use, I gather.
> dev.cpu.0.cx_supported: C1/0
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% last 500us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/0
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% last 500us
>
> >
> > Only spotted a verbose dmesg for 7.2-STABLE there, not for 8.0?
>
> Not, I didn't make one that evening. There is one over ther now. :-)
>
> > I suppose you have HTT disabled in BIOS?
>
> Yes, I had, it is enabled now.
Well I don't imagine running at half speed with HTT is going to be as
quick as full speed without .. and I'll guess further that this is what
the 'non-uniform processors' message is likely about. You may find that
putting a faster non-HTT P4 in it, maybe up to 2.8GHz would go better,
or that search tool shows some 3.06GHz and a 2.40A GHz HTT @533MHz FSB.
HTH, Ian
___
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: Create socket files
On Tue, Dec 22, 2009 at 8: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, > > Forgive my last post, I didn't read your original message in depth. Do you have security.jail.allow_raw_sockets=1 set on host? -- Adam Vande More ___ 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: Create socket files
On Tue, Dec 22, 2009 at 08:34:09PM -0500, Peter Fraser wrote: > > instructions in the handbook to create some jails. It makes part of > the filesystem readonly which is good. 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 13 is EACCES, "The requested address is protected, and the currect user has inadequate permission to access it." Since you have created a read-only file system, I'd say the socket is attempting to bind to a read-write (full-duplex) socket, given the "log" in the name. Just creating the socket is unlikely to be blocked by your read-only file system, since it doesn't consume an i-node until it is bound to a name, or more specifically, the system doesn't know what permissions apply until it is bound. 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 "freebsd-stable-unsubscr...@freebsd.org"
Re: Create socket files
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"
Create socket files
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. 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? ___ 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"
problem with iwi driver in 8.0 and custom kernel (works on generic)
i've got some problems with iwi in Freebsd 8.0, using GENERIC kernel everything works just fine, compiling a custom kernel, just excluding some modules i don't need, cause an interrupt storm to happen on irq11: Dec 22 22:35:18 legend kernel: iwi0: mem 0xb0101000-0xb0101fff irq 10 at device 4.0 on pci6 Dec 22 22:35:18 legend kernel: iwi0: [ITHREAD] Dec 22 22:35:22 legend kernel: wlan0: Ethernet address: xx:xx:xx:xx:xx:xx Dec 22 22:35:32 legend kernel: interrupt storm detected on "irq11:"; throttling interrupt source Dec 22 22:35:33 legend kernel: iwi0: timeout waiting for iwi_bss firmware initialization to complete Dec 22 22:35:33 legend kernel: iwi0: could not load boot firmware iwi_bss maybe these other info from dmesg could be of some help to track down the problem: Dec 22 21:46:45 legend kernel: pcib1: irq 11 at device 28.0 on pci0 Dec 22 21:46:45 legend kernel: pci9: on pcib1 Dec 22 21:46:45 legend kernel: pcib2: irq 10 at device 28.1 on pci0 Dec 22 21:46:45 legend kernel: pci10: on pcib2 Dec 22 21:46:45 legend kernel: pcib3: irq 9 at device 28.2 on pci0 Dec 22 21:46:45 legend kernel: pci2: on pcib3 Dec 22 21:46:45 legend kernel: uhci0: USB controller USB-A> port 0x1820-0x183f irq 11 at device 29.0 on pci0 Dec 22 21:46:45 legend kernel: uhci0: [ITHREAD] Dec 22 21:46:45 legend kernel: uhci0: LegSup = 0x003b Dec 22 21:46:45 legend kernel: usbus0: USB controller USB-A> on uhci0 Dec 22 21:46:45 legend kernel: uhci1: USB controller USB-B> port 0x1840-0x185f irq 11 at device 29.1 on pci0 Dec 22 21:46:45 legend kernel: uhci1: [ITHREAD] Dec 22 21:46:45 legend kernel: uhci1: LegSup = 0x0010 Dec 22 21:46:45 legend kernel: usbus1: USB controller USB-B> on uhci1 Dec 22 21:46:45 legend kernel: uhci2: USB controller USB-C> port 0x1860-0x187f irq 9 at device 29.2 on pci0 Dec 22 21:46:45 legend kernel: uhci2: [ITHREAD] Dec 22 21:46:45 legend kernel: uhci2: LegSup = 0x0010 Dec 22 21:46:45 legend kernel: usbus2: USB controller USB-C> on uhci2 Dec 22 21:46:45 legend kernel: uhci3: USB controller USB-D> port 0x1880-0x189f irq 10 at device 29.3 on pci0 Dec 22 21:46:45 legend kernel: uhci3: [ITHREAD] Dec 22 21:46:45 legend kernel: uhci3: LegSup = 0x0010 Dec 22 21:46:45 legend kernel: usbus3: USB controller USB-D> on uhci3 Dec 22 21:46:45 legend kernel: ehci0: controller> mem 0xb004-0xb00403ff irq 11 at device 29.7 on pci0 Dec 22 21:46:45 legend kernel: ehci0: [ITHREAD] Dec 22 21:46:45 legend kernel: usbus4: EHCI version 1.0 Dec 22 21:46:45 legend kernel: usbus4: controller> on ehci0 Dec 22 21:46:45 legend kernel: pcib4: at device 30.0 on pci0 Dec 22 21:46:45 legend kernel: pci_link6: BIOS IRQ 11 for 6.1.INTA is invalid Dec 22 21:46:45 legend kernel: pci6: on pcib4 Dec 22 21:46:45 legend kernel: pcib4: no PRT entry for 6.4.INTA Dec 22 21:46:45 legend kernel: cbb0: mem 0xb010-0xb0100fff irq 9 at device 1.0 on pci6 Dec 22 21:46:45 legend kernel: cardbus0: on cbb0 Dec 22 21:46:45 legend kernel: pccard0: <16-bit PCCard bus> on cbb0 Dec 22 21:46:45 legend kernel: cbb0: [FILTER] i did read somewhere in the forums/mls that a patch was on STABLE to solve a interrupt storm related to PCI: could it be related to this? is there a patch i can apply to get rid of this problem? (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.) thanks regards ocean ___ 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: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?
Hello have you looked to your /etc/rc.conf set to the following by adding: powerd_enable="YES" power_flag'-i 85 -r 60 -p 100" or Now you can also modify this file: /etc/sysctl.conf or /boot/loader.conf (CPU Frequency) debug.cpufreq.lowest=600 To test live in your terminal you can set it with this command: sysctl debug.cpufreq.lowest=600 Now you can set it to 1200 but I would recommend 100 at a time for testing. Thank You Sean Hulbert Miraculum Laborat Network Systems Specialist www.toolwire.com CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication. igitur qui desiderat pacem, praeparet bellum!!! Epitoma Rei Militaris -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Torfinn Ingolfsen Sent: Tuesday, December 22, 2009 3:42 PM To: freebsd-stable@freebsd.org Subject: Re: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"? On Mon, 21 Dec 2009 21:21:45 + (GMT) Gavin Atkinson wrote: > Can you please reboot and show a verbose dmesg from this system? Yes, it is there[1] now. :-) > Also, how many CPUs does this system actually have? It appears that > in the 7.2 dmesg at 2) above, two are detected but only one is ever > used - are you explicitly disabling hyperthreading somehow? It has one Pentium 4 cpu. Hyperthreading was disabled in bios, it is enabled now: 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.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009 r...@kg-work2.kg4.no:/usr/obj/usr/src/sys/SX270 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 2145849344 (2046 MB) avail memory = 2090192896 (1993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard References: 1) http://sites.google.com/site/tingox/sx260_freebsd -- Torfinn ___ 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: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?
On Tuesday 22 December 2009 06:41:30 pm Torfinn Ingolfsen wrote: > On Mon, 21 Dec 2009 21:21:45 + (GMT) > > FreeBSD 7.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009 > CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbff CA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FX SR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x4400 > Logical CPUs per core: 2 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > ioapic0: Changing APIC ID to 2 My first thought was that perhaps you were running a uniprocessor kernel, but I checked GENERIC and SMP option is there. My dmesg is a little different: FreeBSD 8.0-STABLE #16: Sat Dec 19 22:56:44 EST 2009 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d AMD Features=0x2010 TSC: P-state invariant FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 I think the clue to run down is why does FreeBSD think your sx260 is running at 1295.21-MHz. I think I would try updating your usb stick's kernel with 8-stable and rebuild it. I'm wondering if someone who made the stick image turned off SMP to make i fit on small sticks (above is 7.2-stable, not the 8 on a stick). I see HTT in your CPUs features, but I wonder what that's based on. What if the BIOS supports hyperthreading but the cpu doesn't? (there were p4 processors sold before hyperthreading came out, I know, I bought one. 8o) You might try finding a cpu diagnostic tool that describes the cpu in great detail, like from download.com, etc. You might also go to Intel's site and lookup the id 0xf29 and see if Intel says it actually supports hyperthreading. ___ 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: Hacked - FreeBSD 7.1-Release
Hello This is my 6 step check list to bullet proof your any Unix box and render it unhackable by remote access. 1. Jail all services that will touch the open internet 2. Enable file and directory security such as using Tripwire or your distro file integrity program 3. Disable any non used services 4. Set IPchains to allow access to only the services you want the outside to access. 5. Off load your system logs to a NFS mount 6. Set a pass phrase for the password. *7. Make sure the computer you are using to access the Unix system is secure and does not have any key logging Trojans on it or "all is for not." Thank You Sean Hulbert Miraculum Laborat Network Systems Specialist www.toolwire.com CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication. igitur qui desiderat pacem, praeparet bellum!!! Epitoma Rei Militaris -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Andresen, Jason R. Sent: Tuesday, December 22, 2009 8:36 AM To: FreeBSD-STABLE Mailing List Subject: RE: Hacked - FreeBSD 7.1-Release Squirrel wrote: >most likely could be some kind of remote code execution or SQLi >executed in the context of some php scripts, you should audit php code >of your web interface and of the websites you host. >also consider the strenght of your passwords, lots of login attempts to >ssh/ftp may mean a he has tried a bruteforce (or a dictionary attack >maybe). you should also check webmin logs, there are a few bruteforcer >for webmin out there, (*hint*) consider the lenght of your average >password if it's more than 7-8 characters aplhanumeric with simbols >most likely this isn't the case. While it's true that it's a good idea to check your password strength, pretty much any host connected to the internet is going to be hit daily by bots looking for weak passwords. It's one area where you logs don't help much because there is too much noise. ___ 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: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?
On Mon, 21 Dec 2009 21:21:45 + (GMT) Gavin Atkinson wrote: > Can you please reboot and show a verbose dmesg from this system? Yes, it is there[1] now. :-) > Also, how many CPUs does this system actually have? It appears that > in the 7.2 dmesg at 2) above, two are detected but only one is ever > used - are you explicitly disabling hyperthreading somehow? It has one Pentium 4 cpu. Hyperthreading was disabled in bios, it is enabled now: 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.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009 r...@kg-work2.kg4.no:/usr/obj/usr/src/sys/SX270 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 real memory = 2145849344 (2046 MB) avail memory = 2090192896 (1993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard References: 1) http://sites.google.com/site/tingox/sx260_freebsd -- Torfinn ___ 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: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?
On Mon, 21 Dec 2009 15:29:54 +1100 (EST) Ian Smith wrote: > Why is it booting up at half speed? Same in your 7.2-STABLE dmesg. I don't know. Since last time, I've upgraded the bios to the latest (A03) and reset bios to default values - but the problem is still there. According to the specs, a SX260 supports all Pentium 4 cpus with 400 MHz and 533 MHz FSB (front side bus). > Something set that way in BIOS? What does 'sysctl dev.cpu' say? The only setting in bios related to cpu speed are "normal" and "comaptible". I've tried both - doesn't make a difference. Now sysctl.dev.cpu says: r...@kg-work2# sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 1295 dev.cpu.0.freq_levels: 1295/-1 1133/-1 971/-1 809/-1 647/-1 485/-1 323/-1 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% last 500us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% last 500us > > Only spotted a verbose dmesg for 7.2-STABLE there, not for 8.0? Not, I didn't make one that evening. There is one over ther now. :-) > I suppose you have HTT disabled in BIOS? Yes, I had, it is enabled now. -- Regards, Torfinn Ingolfsen ___ 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: Hacked - FreeBSD 7.1-Release
Squirrel wrote: >most likely could be some kind of remote code execution or SQLi executed >in the context of some php scripts, you should audit php code of your >web interface and of the websites you host. >also consider the strenght of your passwords, lots of login attempts to >ssh/ftp may mean a he has tried a bruteforce (or a dictionary attack >maybe). you should also check webmin logs, there are a few bruteforcer >for webmin out there, (*hint*) consider the lenght of your average >password if it's more than 7-8 characters aplhanumeric with simbols most >likely this isn't the case. While it's true that it's a good idea to check your password strength, pretty much any host connected to the internet is going to be hit daily by bots looking for weak passwords. It's one area where you logs don't help much because there is too much noise. ___ 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: Changing ISO filenames
On Tue, 2009-12-22 at 19:28 +0100, Oliver Pinter wrote: > Do you have any plans, when comming out REL_6.5 and REL_7.3? There are no plans for 6.5-RELEASE, 6.4-RELEASE was the last of the official releases for the stable/6 branch. We just started working out a schedule for 7.3-RELEASE, I should be sending that out some time next week. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: Disc lock up on 8.0-STABLE
Interesting... I just got another hard lock on the system, not at 3am this time. The only other common factor in this is that the lockup is always preceeded by a flood of failed ssh logins. I;m sure we've all seen these - I get them on every BSD system I have - they look like this: Dec 22 17:37:10 turpentine sshd[8188]: error: PAM: authentication error for illegal user kevin from 61.74.75.43 Dec 22 17:43:21 turpentine sshd[9983]: error: PAM: authentication error for illegal user kevin from 58.60.106.24 Dec 22 17:49:30 turpentine sshd[11781]: error: PAM: authentication error for illegal user kevin from 219.234.95.164 Dec 22 18:01:47 turpentine sshd[15435]: error: PAM: authentication error for illegal user kevin from 61.74.75.43 Dec 22 18:07:54 turpentine sshd[17259]: error: PAM: authentication error for illegal user kevin from 61.74.75.43 Dec 22 18:14:06 turpentine sshd[19282]: error: PAM: authentication error for illegal user kevin from 61.74.75.53 Theres always a flood of those on the console immediately preceeding the lockup. So this time it cant have been anything to do with the 3am run. -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"
Re: Changing ISO filenames
Hi! Do you have any plans, when comming out REL_6.5 and REL_7.3? On 12/21/09, Ken Smith wrote: > > People who collect ISO images from more than just the FreeBSD Project > have been mentioning it would be nice if "FreeBSD" was part of the > filenames for a while now. I just committed a change to head that will > add "FreeBSD-" to the beginning of the filenames. So for example > > 9.0-RELEASE-amd64-dvd1.iso > > becomes > > FreeBSD-9.0-RELEASE-amd64-dvd1.iso > > As part of the commit I set a 1-week MFC timer and at that point I will > MFC the change to all of the branches we currently target for the > Monthly Snapshots (so all the way back to stable/6). That way the > filenames will be consistent for all the images generated for the > January 2010 Monthly Snapshots. > > -- > Ken Smith > - From there to here, from here to | kensm...@buffalo.edu > there, funny things are everywhere. | > - Theodore Geisel | > > ___ 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: Changing ISO filenames
On Mon, Dec 21, 2009 at 6:50 AM, Ken Smith wrote: > > People who collect ISO images from more than just the FreeBSD Project > have been mentioning it would be nice if "FreeBSD" was part of the > filenames for a while now. I just committed a change to head that will > add "FreeBSD-" to the beginning of the filenames. So for example > >9.0-RELEASE-amd64-dvd1.iso > > becomes > >FreeBSD-9.0-RELEASE-amd64-dvd1.iso > > As part of the commit I set a 1-week MFC timer and at that point I will > MFC the change to all of the branches we currently target for the > Monthly Snapshots (so all the way back to stable/6). That way the > filenames will be consistent for all the images generated for the > January 2010 Monthly Snapshots. > > -- >Ken Smith > - From there to here, from here to | kensm...@buffalo.edu > there, funny things are everywhere. | > - Theodore Geisel | > > I liked this change ( appending FreeBSD- in front .iso file names ) very much because always I was adding this to downloaded file names . This change will allow also inclusion of these file names in internet search lists . Thank you very much . Mehmet Erol Sanliturk ___ 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: Disc lock up on 8.0-STABLE
> Ehm... what happens if you just run daily by hand? Nothingm ... that was the first thing I tried :( ___ 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: Disc lock up on 8.0-STABLE
On Tue, 22 Dec 2009, Pete French wrote: > > Same here! > > I am wondering what happens if I disable the automatic run, > then wait until 3am and run by hand... possibly its something > to do with the data it is having to work on at 3am ? > > > But the box has been running 8-STABLE since around end of August, and > > the first time it happened was about 10-14 days ago, after i upgraded > > world+kernel. > > Ah, so theres a version of 8 before which it doesnt do it ? Now that > is interesting! I am running 8.-STABLE, but possibly if I go > back to 8.0-RELEASE then I might not see this ? Ehm... what happens if you just run daily by hand? # /usr/sbin/periodic daily Then you can at least have a chance to monitor what it does... (instead of being awake at 03.00) /Bjorn ___ 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: Disc lock up on 8.0-STABLE
> Same here! I am wondering what happens if I disable the automatic run, then wait until 3am and run by hand... possibly its something to do with the data it is having to work on at 3am ? > But the box has been running 8-STABLE since around end of August, and > the first time it happened was about 10-14 days ago, after i upgraded > world+kernel. Ah, so theres a version of 8 before which it doesnt do it ? Now that is interesting! I am running 8.-STABLE, but possibly if I go back to 8.0-RELEASE then I might not see this ? -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"
Re: Disc lock up on 8.0-STABLE
On 12/22/09 3:19 PM, Pete French wrote: >> As the box is remote with only ssh access, it's a little difficult to >> debug this. During the weekend i waited till 3 o'clock with a top >> running, and saw that hundreds/thousands of /bin/sh processes were >> started. After that i commented out periodic daily in /etc/crontab, that >> "solved" the problem for me. > > Interesting - I have tried running the daily periodic processes by hand, but > that does not trigger it. Possibly it is something about being run from > cron maybe ? Same here! > >> I was not able to debug this any further yet, i have one other box with >> all UFS and a ZFS backup disc also running latest 8-STABLE but it does >> not exhibit the problem. > > Same here :-( My other box is identical hardware and almost config (UFS > and ZFS) but it works fine. > > I am not sure that ym debug kernel will help now - assuming this is the > same thing as you are seeing, it sounds like a process running amok rather > than any kernel bug. Was yoour system a fresh install, or an upgrade from > 7-STABLE ? I'm not 100% sure anymore, but i think i installed 7.2-RELEASE set hw.pci.mcfg=0 in loader.conf due to 8.0-BETAX not detecting the discs without it and then immediately upgrading to 8-STABLE. But the box has been running 8-STABLE since around end of August, and the first time it happened was about 10-14 days ago, after i upgraded world+kernel. When the problem occurs and you happen to have a shell everything you try to run is being rejected with an error no resources for fork or something. I had to enter reboot like 30 times before the box rebooted. So with a bit of patience one will be able to get aditional information out of the box. Cheers, Florian ___ 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: 8-STABLE: support for this SMB controller?
Jeremy Chadwick wrote: > Is the board you're using a i7-920 in a server-class board? If so, let > me know the manufacturer, exact model/revision number, and the output > from "kenv | grep smbios" and I'll see if I can wrangle details out of > them. Hm... it is not. It is a Desktop board - ASRock X58 Extreme. smbios.bios.reldate="11/06/2009" smbios.bios.vendor="American Megatrends Inc." smbios.bios.version="P1.60" smbios.chassis.maker="To Be Filled By O.E.M." smbios.chassis.serial="To Be Filled By O.E.M." smbios.chassis.tag="To Be Filled By O.E.M." smbios.chassis.version="To Be Filled By O.E.M." smbios.memory.enabled="6291456" smbios.planar.maker="ASRock" smbios.planar.product="X58 Extreme" smbios.planar.serial=" " smbios.planar.version=" " smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="To Be Filled By O.E.M." smbios.system.product="To Be Filled By O.E.M." smbios.system.serial="To Be Filled By O.E.M." smbios.system.uuid="00020003-0004-0005-0006-000700080009" smbios.system.version="To Be Filled By O.E.M." smbios.version="2.5" -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ 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: 8-STABLE: support for this SMB controller?
On Tue, 22 Dec 2009 08:57:54 +0300 Yuri Pankov wrote: > On Tue, Dec 22, 2009 at 06:51:04AM +0100, Oliver Lehmann wrote: > > Andriy Gapon wrote: > > Hm so I guess there is no other way in determining the CPUs > > temperature? > > Tried coretemp(4) yet? And for those running AMD cpus there is amdtemp(4). -- Regards, Torfinn Ingolfsen ___ 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: Disc lock up on 8.0-STABLE
on 22/12/2009 15:49 Florian Smeets said the following: > Dec 20 03:03:22 XXX kernel: maxproc limit exceeded by uid 0, please see > tuning(7) and login.conf(5). > Dec 20 03:03:53 XXX last message repeated 31 times This seems to be superficially similar to infamous "fork bomb". Would you be able to reproduce this and get 'ps axl' when that starts happening. Alternatively, you may try SW_WATCHDOG kernel option together with watchdogd. That could produce a useful crash dump if/when the system freezes. -- Andriy Gapon ___ 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: Disc lock up on 8.0-STABLE
> i'm trying to track down the same problem. The box in question has > everything on UFS (mirrored ataraid) and a backup disk with ZFS on it > attached to USB. This is very interesting to know! It seems you have managed to get a lot more information out of it than I have. > As the box is remote with only ssh access, it's a little difficult to > debug this. During the weekend i waited till 3 o'clock with a top > running, and saw that hundreds/thousands of /bin/sh processes were > started. After that i commented out periodic daily in /etc/crontab, that > "solved" the problem for me. Interesting - I have tried running the daily periodic processes by hand, but that does not trigger it. Possibly it is something about being run from cron maybe ? > I was not able to debug this any further yet, i have one other box with > all UFS and a ZFS backup disc also running latest 8-STABLE but it does > not exhibit the problem. Same here :-( My other box is identical hardware and almost config (UFS and ZFS) but it works fine. I am not sure that ym debug kernel will help now - assuming this is the same thing as you are seeing, it sounds like a process running amok rather than any kernel bug. Was yoour system a fresh install, or an upgrade from 7-STABLE ? -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"
Re: Disc lock up on 8.0-STABLE
On 12/22/09 1:16 PM, Pete French wrote: > I've been gradually testing 8.0 on several machines propr to deploying it > live, but I currently have a machine which appears to lock-up at 3am > every day. The symptoms are that the machine is still pingable, but doing > anything which requires access to the disc just freezes (so you cant login for > example). I've seen simiilar behaviour behore on machines when the disc > syste has locked up for some reason, so am ttentatively guessing that > this is the cause. > > The machine is an HP DL360 G5 with a ciss0 controller for the drives. > I have upgraded to the latest STABLE but the freeze still happens. > Am including a dmesg below, and will compile it with KDB, DDB to > see what happens. > > The machine is booting from a UFS partition, but is using ZFS for everything > else. The fcat it deadlocks at 3am makes me thing this is something to > do with scheduled jobs maybe ? Then again, I have an almost identical DL360 > which is running 8.0 and is rock solid. > Hi Pete, i'm trying to track down the same problem. The box in question has everything on UFS (mirrored ataraid) and a backup disk with ZFS on it attached to USB. The freeze happens at 3am too, i have these log messages: Dec 20 03:00:00 XXX newsyslog[2810]: logfile turned over due to size>100K Dec 20 03:03:21 XXX kernel: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl. Dec 20 03:03:22 XXX kernel: maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5). Dec 20 03:03:53 XXX last message repeated 31 times I had increased vm.pmap.pv_entry_max and vm.pmap.shpgperproc then only the maxproc limit exceeded message remained. As the box is remote with only ssh access, it's a little difficult to debug this. During the weekend i waited till 3 o'clock with a top running, and saw that hundreds/thousands of /bin/sh processes were started. After that i commented out periodic daily in /etc/crontab, that "solved" the problem for me. I was not able to debug this any further yet, i have one other box with all UFS and a ZFS backup disc also running latest 8-STABLE but it does not exhibit the problem. Cheers, Florian ___ 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: atheros issues with releng_8
On Monday 21 December 2009 9:23:47 pm Zane C. B. wrote: > With the GENERIC kernel on releng_8 and releng_8_0, I am having > issues with the Atheros wireless on my laptop. > > Upon boot I am getting the message below. > > ath0: irq 17 at device 0.0 on pci3 > ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). > ath0: cannot map register space > device_attach: ath0 attach returned 6 > > Any suggestions? It was working fine on releng_6. You can try disabling ACPI. I have seen ACPI clear BARs in other devices before and FreeBSD doesn't cope well with cleared BARs. -- John Baldwin ___ 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"
Disc lock up on 8.0-STABLE
I've been gradually testing 8.0 on several machines propr to deploying it live, but I currently have a machine which appears to lock-up at 3am every day. The symptoms are that the machine is still pingable, but doing anything which requires access to the disc just freezes (so you cant login for example). I've seen simiilar behaviour behore on machines when the disc syste has locked up for some reason, so am ttentatively guessing that this is the cause. The machine is an HP DL360 G5 with a ciss0 controller for the drives. I have upgraded to the latest STABLE but the freeze still happens. Am including a dmesg below, and will compile it with KDB, DDB to see what happens. The machine is booting from a UFS partition, but is using ZFS for everything else. The fcat it deadlocks at 3am makes me thing this is something to do with scheduled jobs maybe ? Then again, I have an almost identical DL360 which is running 8.0 and is rock solid. -pete. 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 #0: Mon Dec 21 15:42:31 GMT 2009 webad...@florentine.rattatosk:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5345 @ 2.33GHz (2333.43-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0x4e3bd AMD Features=0x2800 AMD Features2=0x1 TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4104138752 (3914 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 20090521 tbfadt-707 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 ACPI Warning: \\_SB_.PCI0.PT02._PRT: Return Package has no elements (empty) 20090521 nspredef-545 pci9: on pcib1 pcib2: at device 0.0 on pci9 pci10: on pcib2 pcib3: at device 0.0 on pci10 pci11: on pcib3 pcib4: at device 1.0 on pci10 pci14: on pcib4 pcib5: at device 2.0 on pci10 pci15: on pcib5 pcib6: at device 0.3 on pci9 pci16: on pcib6 pcib7: at device 3.0 on pci0 pci6: on pcib7 pcib8: at device 0.0 on pci6 pci7: on pcib8 pcib9: at device 4.0 on pci7 pci8: on pcib9 ciss0: port 0x4000-0x40ff mem 0xfde8-0xfdef,0xfde7-0xfde77fff irq 16 at device 8.0 on pci7 ciss0: PERFORMANT Transport ciss0: got 2 MSI messages] ciss0: [ITHREAD] pcib10: at device 4.0 on pci0 pci19: on pcib10 pcib11: at device 5.0 on pci0 pci22: on pcib11 pcib12: at device 6.0 on pci0 pci2: on pcib12 pcib13: at device 0.0 on pci2 pci3: on pcib13 bce0: mem 0xf800-0xf9ff irq 18 at device 0.0 on pci3 miibus0: on bce0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:0b:5f:1f:76 bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C (1.9.6); Flags (MSI|MFW); MFW () pcib14: at device 7.0 on pci0 pci4: on pcib14 pcib15: at device 0.0 on pci4 pci5: on pcib15 bce1: mem 0xfa00-0xfbff irq 19 at device 0.0 on pci5 miibus1: on bce1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce1: Ethernet address: 00:1e:0b:5f:fd:d8 bce1: [ITHREAD] bce1: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C (1.9.6); Flags (MSI|MFW); MFW () uhci0: port 0x1000-0x101f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0x1020-0x103f irq 17 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0x1040-0x105f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 uhci3: port 0x1060-0x107f irq 19 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: on uhci3 ehci0: mem 0xf7df-0xf7df03ff irq 16 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: on ehci0 pcib16: at device 30.0 on pci0 pci1: on pcib16 vgapci0: port 0x3000-0x30ff mem 0xd800-0xdfff,0xf7ff-0xf7ff irq 23 at device 3.0 on pci1 pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) uhci4: port 0x3800-0x381f irq 22 at device 4.4 on pci1 uhci4: [ITHREAD] usbus5: on uhci4 pci1: at device 4.6 (no driver attached) isab0: at dev
Re: atheros issues with releng_8
On Dec 21, 2009, at 10:37 PM, "Zane C.B." wrote: On Mon, 21 Dec 2009 22:32:40 -0500 Dan Langille wrote: Zane C.B. wrote: With the GENERIC kernel on releng_8 and releng_8_0, I am having issues with the Atheros wireless on my laptop. Upon boot I am getting the message below. ath0: irq 17 at device 0.0 on pci3 ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). ath0: cannot map register space device_attach: ath0 attach returned 6 Any suggestions? It was working fine on releng_6. http://www.freebsddiary.org/wireless-8.php Been there, done that, documented it. Enjoy. :) Read the dmesg output I pasted. This is totally unrelated to it. The dmesg output shows the device as never being attached do to a it not being able to map the register space. Ahh yes. Sorry. I missed that. Your interpretation of the situation helps. -- Dan Langille http://langille.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: FreeBSD 7.2-STABLE make installworld ERROR
Thanks Yuri. It solve my problem :) Best Regards! 2009/12/22 Yuri Pankov : > On Tue, Dec 22, 2009 at 01:52:14PM +0800, James Chang wrote: >> Dears, >> >> Today, I use ctm upgrade my FreeBSD source code to "src-7 859" >> When I try to make world, in make buildworld stage it show me "World >> build completed on Tue Dec 22 12:57:30 CST 2009" >> But when I execute "make installworld" it show me the following ERROR >> message: >> >> ===> sys/boot/i386/btx (install) >> ===> sys/boot/i386/btx/btx (install) >> ===> sys/boot/i386/btx/btxldr (install) >> ===> sys/boot/i386/btx/lib (install) >> ===> sys/boot/i386/boot2 (install) >> cc -Os -fno-guess-branch-probability -fomit-frame-pointer >> -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx >> -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 >> -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 >> -I/usr/src/sys/boot/i386/boot2/../../common >> -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall >> -Waggregate-return -Wbad-function-cast -Wcast-align >> -Wmissing-declarations -Wmissing-prototypes -Wnested-externs >> -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline >> --param max-inline-insns-single=100 -ffreestanding >> -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >> -mno-sse3 -m32 -march=i386 -S -o boot2.s.tmp >> /usr/src/sys/boot/i386/boot2/boot2.c >> sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s >> rm -f boot2.s.tmp >> as --32 -o boot2.o boot2.s >> ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 >> -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o >> boot2.o sio.o >> objcopy -S -O binary boot2.out boot2.bin >> btxld -v -E 0x2000 -f bin -b >> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >> boot2.ld -P 1 boot2.bin >> btxld:No such file or directory >> *** Error code 1 >> >> Stop in /usr/src/sys/boot/i386/boot2. >> *** Error code 1 >> >> Stop in /usr/src/sys/boot/i386. >> *** Error code 1 >> >> Stop in /usr/src/sys/boot. >> *** Error code 1 >> >> Stop in /usr/src/sys. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> >> = >> PS. My "uname -a" before make installworld >> FreeBSD db1.books.com.tw 7.2-STABLE FreeBSD 7.2-STABLE #1: Thu Dec 3 >> 23:08:26 CST 2009 >> r...@db1.books.com.tw:/usr/obj/usr/src/sys/GENERIC amd64 >> >> >> Best Regards! > > Looks like > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028377.html > > > Yuri > ___ 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: atheros issues with releng_8
On Mon, Dec 21, 2009 at 10:32:40PM -0500, Dan Langille wrote: > Zane C.B. wrote: > >With the GENERIC kernel on releng_8 and releng_8_0, I am having > >issues with the Atheros wireless on my laptop. > > > >Upon boot I am getting the message below. > > > >ath0: irq 17 at device 0.0 on pci3 > >ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). > >ath0: cannot map register space > >device_attach: ath0 attach returned 6 > > > >Any suggestions? It was working fine on releng_6. > > http://www.freebsddiary.org/wireless-8.php > > Been there, done that, documented it. The attach that fails happen long before wlan devices and user level ifconfigs. Maybe "pciconf -lv" will show something or maybe showing some of the pci space with pciconf -r will give an idea why the attach fails. John -- John Hay -- j...@meraka.csir.co.za / j...@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: atheros issues with releng_8
On Mon, 21 Dec 2009 21:53:00 -0500 Steven Friedrich wrote: > On Monday 21 December 2009 09:23:57 pm Zane C.B. wrote: > > With the GENERIC kernel on releng_8 and releng_8_0, I am having > > issues with the Atheros wireless on my laptop. > > > > Upon boot I am getting the message below. > > > > ath0: irq 17 at device 0.0 on pci3 > > ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). > > ath0: cannot map register space > > device_attach: ath0 attach returned 6 > > > > Any suggestions? It was working fine on releng_6. > > > > This is not even remotely close to the issue I am having. I am also aware of this. The issue is the ath device is not attaching because of the issue shown in the dmesg chunk I included with the original message and below. ath0: irq 17 at device 0.0 on pci3 ath0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x). ath0: cannot map register space device_attach: ath0 attach returned 6 signature.asc Description: PGP signature
