aac support for Adaptec 2020SA ZCR
We have a motherboard (Supermicro X6DHT-G) with an Adaptec 2020SA SATA RAID controller. We have been unable to get any drives recognised by the FreeBSD 5.3 release installation CD, and we've been unable to find much discussion about the status of the AAC device and support for this chipset. Several other Adaptec SATA RAID controllers seem to be supported: 2410SA, 2810SA, 21610SA. The logical drive configured in the RAID controller is detected successfully in a Gentoo Linux 2004.3 environment. Has anyone had success with this controller? Any alternative you would recommend or will support be available in 5.4? I believe from the source code that the driver is maintained by Scott Long and that recent changes have been taking place. Thanks for any assistance. Ari Maniatis -- ish group pty ltd http://www.ish.com.au 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: aac support for Adaptec 2020SA ZCR
Aristedes Maniatis wrote: We have a motherboard (Supermicro X6DHT-G) with an Adaptec 2020SA SATA RAID controller. We have been unable to get any drives recognised by the FreeBSD 5.3 release installation CD, and we've been unable to find much discussion about the status of the AAC device and support for this chipset. Several other Adaptec SATA RAID controllers seem to be supported: 2410SA, 2810SA, 21610SA. The logical drive configured in the RAID controller is detected successfully in a Gentoo Linux 2004.3 environment. Has anyone had success with this controller? Any alternative you would recommend or will support be available in 5.4? I believe from the source code that the driver is maintained by Scott Long and that recent changes have been taking place. You might be interested in this article: http://hardware.slashdot.org/hardware/05/03/20/1944233.shtml?tid=198tid=190tid=172tid=137tid=7 I don't know how FreeBSD is related, but it's probably is. Thanks for any assistance. Ari Maniatis -- ish group pty ltd http://www.ish.com.au 7 Darghan St Glebe 2037 Australia phone +61 2 9660 1400 fax +61 2 9660 7400 PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Uzi Klein Software Development Executive http://www.bmby.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with world build in RELENG_5_4
Hi, I found a little problem with RELENG_5_4 buildworld in my env. I have a little patched RELENG_5_4 src in a local cvs server, mounted ro,-L in the build machine (/usr/src) No rpc.lockd or rpc.statd daemon running in both machines. build machine timesync with cvs server by ntpdate before build. Every time I do a rm -rf /usr/obj/* cd /usr/src make buildworld I get: cc -Os -fno-strict-aliasing -mtune=athlon-xp -pipe -I. -I/usr/src/usr.sbin/confi g -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/l egacy/usr/lib -o config config.o main.o lang.o mkmakefile.o mkheaders.o mkoption s.o -ll -legacy sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 config /usr/obj/usr/sr c/i386/legacy/usr/sbin -- stage 2.1: cleaning up the object tree -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE =pentium-mmx GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin GROFF_FONT_PA TH=/usr/obj/usr/src/i386/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/u sr/src/i386/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/i386 INSTAL L=sh /usr/src/tools/install.sh PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/us r/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/ob j/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/ games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 DESTDIR=/usr/obj/usr/s rc/i386 par-cleandir === share/info === include rm -f osreldate.h version vers.c rm: version: Read-only file system *** Error code 1 The only thing I change form previous week builds are the -L mount and disabling the rpc.lockd and rpc.statd daemons in both machines. I can solve the problem doing a make obj before make buildworld. Can someone reproduce this? thanks in advance, -- josemi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
libieee1284 and canon parallel scanners
Hi, I'm desperately trying to get my parallel port scanner to work on FreeBSD 5-STABLE. It is a canon 640P scanner, that in theory should work with sane-backends and canon_pp driver (which depends on libieee1284). Instead, it can't detect the scanner. I posted to sane-devel to try to get some feedback, however there may be some FreeBSD-specific issues (see http://lists.alioth.debian.org/pipermail/sane-devel/2005-April/013400.html ). (please see the link for details). In summary: dmesg under FreeBSD shows: ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 libieee1284 is installed, if you run the test utility you get: Found 3 ports: 0x278: 0x378: 0x3bc: 0x278: 0x278 RAW NIBBLE BYTE COMPAT ECPSWE 0x378: 0x378 RAW NIBBLE BYTE COMPAT ECPSWE 0x3bc: 0x3bc RAW NIBBLE BYTE COMPAT ECPSWE But the scanner is not detected! Sorry if this post is a little off-topic, I'm looking for parallel port gurus who might be able to help. e.g. do I need some random SCSI driver or something. Cheers, Rob Pollock. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
accessing USB device with long Initialization
Hello, I've upgraded to 5.4-RC1 and I'd like to access an Mpman MP3 Player via USB. When I attach the USB device several messages appear and the Mpman displays Starting but then /dev/da0 is not available. The messages look like this: 11:12:22: umass0: vendor 0x10d6 Generic USB Disk Device, rev 1.10/1.00, addr 2 11:12:22: da0 at umass-sim0 bus 0 target 0 lun 0 11:12:22: da0: GENERIC USB DISK DEVICE 1.00 Removable Direct Access SCSI-2 device 11:12:22: da0: 1.000MB/s transfers 11:12:22: da0: 123MB (252509 512 byte sectors: 64H 32S/T 123C) 11:12:24: umass0: BBB reset failed, STALLED 11:12:24: umass0: BBB bulk-in clear stall failed, STALLED 11:12:24: umass0: BBB bulk-out clear stall failed, STALLED 11:12:24: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 11:12:24: umass0: BBB reset failed, STALLED 11:12:24: umass0: BBB bulk-in clear stall failed, STALLED 11:12:24: umass0: BBB bulk-out clear stall failed, STALLED 11:12:24: umass0: BBB reset failed, STALLED 11:12:24: umass0: BBB bulk-in clear stall failed, STALLED 11:12:24: umass0: BBB bulk-out clear stall failed, STALLED 11:12:24: umass0: BBB reset failed, STALLED 11:12:24: umass0: BBB bulk-in clear stall failed, STALLED 11:12:24: umass0: BBB bulk-out clear stall failed, STALLED 11:12:24: umass0: BBB reset failed, STALLED 11:12:24: umass0: BBB bulk-in clear stall failed, STALLED 11:12:24: umass0: at uhub2 port 1 (addr 2) disconnected 11:12:24: (da0:umass-sim0:0:0:0): lost device 11:12:24: (da0:umass-sim0:0:0:0): removing device entry 11:12:24: Opened disk da0 - 5 11:12:24: umass0: detached For comparison 5.3 calls the kernel debugger and NetBSD waits a little longer and then allows access on the Mpman. Can I make 5.4-RC1 allow accessing the Mpman? -Hanspeter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel errors : AE_NOT_FOUND
Eric Marquez wrote: I recently notice these errors in my dmesg. Can somebody help explain this to me. Do I need to worry about this? Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x591 Stepping = 1 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 268419072 (255 MB) avail memory = 253014016 (241 MB) K6-family MTRR support enabled (2 registers) ACPI-0277: *** Warning: Invalid checksum in table [DSDT] (23, sum fc is not zero) ACPI-0452: *** Error: Looking up [PIRQ] in namespace, AE_NOT_FOUND ACPI-1303: *** Error: [NULL NAME], AE_NOT_FOUND ACPI-0204: *** Error: AcpiLoadTables: Could not load namespace: AE_NOT_FOUND ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NOT_FOUND ACPI: table load failed: AE_NOT_FOUND --ebm ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] You could look: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html at the 11.16.4 ASL, acpidump, and IASL point This is a DSDT problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
minority tolarated?
Hello, The Beastie menu makes it convenient choosing boot options. The Beastie decorating space right to the menu reflects the preference of the majority or all of the FreeBSD developers. Their opinion is documented in http://www.freebsd.org/copyright/daemon.html . However there are users which have a different opinion and which don't like the Beastie mascot to be displayed during boot time. However there are users which have a different opinion and which don't like the Beastie mascot to be displayed during boot time. The question is: are such users - welcome - tolerated - disliked. In case they are more or less tolerated what should they do in order to switch the Beastie splash screen? - renounce of the Beastie menu (beastie_disable=YES) ? - spend some hours to dig in mailing lists or dig in http://www.forth.org/tutorials.html ? - or have an convenient flag in loaders.conf that allows to run Beastie menu but display some other decoration? The patch 74577 offers a convenient flag to disable the display of the Beastie while being compatible with the majority of the FreeBSD developers. http://www.freebsd.org/cgi/query-pr.cgi?pr=74577 There were talks that the FreeBSD logo will change anyway. But so far this has not affected 5.4-RC1. -Hanspeter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
two mysterious files in RELENG_5_4
Hello all. I have FreeBSD 5.4-RC1 installed from FTP. Today I ran cvsup to get the latest RELENG_5_4 src-all. I've seen two strange files were checkouted by cvsup: Checkout src/installworld_newk Checkout src/installworld_oldk I don't see those files on http://www.freebsd.org/cgi/cvsweb.cgi/src/?only_with_tag=RELENG_5_4 but I see them on http://www.freebsd.org/cgi/cvsweb.cgi/src/Attic/ According to the cvsweb logs those files were removed in HEAD but still exist in RELENG_5_4. But why I don't see them on the cvsweb by the first URL and why they didn't exist in my 5.4-RC1 before cvsup? Or, if they were removed in the RELENG_5_4 too, why cvsup checkouted them today? Following is my cvsup supfile: # Defaults that apply to all the collections # *default host=cvsup.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_5_4 *default delete use-rel-suffix *default compress ## Main Source Tree. # src-all ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: aac support for Adaptec 2020SA ZCR
Aristedes Maniatis wrote: We have a motherboard (Supermicro X6DHT-G) with an Adaptec 2020SA SATA RAID controller. We have been unable to get any drives recognised by the FreeBSD 5.3 release installation CD, and we've been unable to find much discussion about the status of the AAC device and support for this chipset. Several other Adaptec SATA RAID controllers seem to be supported: 2410SA, 2810SA, 21610SA. The logical drive configured in the RAID controller is detected successfully in a Gentoo Linux 2004.3 environment. Has anyone had success with this controller? Any alternative you would recommend or will support be available in 5.4? I believe from the source code that the driver is maintained by Scott Long and that recent changes have been taking place. Thanks for any assistance. Ari Maniatis The 2020 seems to be in a pre-release phase just for SuperMicro. It's not mentioned at all on the Adaptec website. I've been in contact with Adaptec engineers who are preparing updates for the FreeBSD driver for it, but it's looking unlikely that they will be done in time for the 5.4 release. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: aac support for Adaptec 2020SA ZCR
Uzi Klein wrote: Aristedes Maniatis wrote: We have a motherboard (Supermicro X6DHT-G) with an Adaptec 2020SA SATA RAID controller. We have been unable to get any drives recognised by the FreeBSD 5.3 release installation CD, and we've been unable to find much discussion about the status of the AAC device and support for this chipset. Several other Adaptec SATA RAID controllers seem to be supported: 2410SA, 2810SA, 21610SA. The logical drive configured in the RAID controller is detected successfully in a Gentoo Linux 2004.3 environment. Has anyone had success with this controller? Any alternative you would recommend or will support be available in 5.4? I believe from the source code that the driver is maintained by Scott Long and that recent changes have been taking place. You might be interested in this article: http://hardware.slashdot.org/hardware/05/03/20/1944233.shtml?tid=198tid=190tid=172tid=137tid=7 I don't know how FreeBSD is related, but it's probably is. FreeBSD != OpenBSD. Let's please not drag that rubbish flamewar onto our technical lists. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
netstat -m broken.
I'm runing 5.4-STABLE on an dual processor amd64. I'm using the network pretty heavily (dual GigE interfaces doing 300 megabit each) and my netstat -m is giving odd results: [1:31:[EMAIL PROTECTED]:~ netstat -m 25927 mbufs in use 18446744073709547405/512000 mbuf clusters in use (current/max) 0/0/0 sfbufs in use (current/peak/max) 18014398509480043 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines [1:37:[EMAIL PROTECTED]:~ netstat -m 18446744073709550967 mbufs in use 4315/512000 mbuf clusters in use (current/max) 0/0/0 sfbufs in use (current/peak/max) 8467 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines ... many of the numbers get really big like that. this machine was just booted. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel killing processes when out of swap
Just had a problem with a box where it looks like it ran out of swap due to a problem process, not a problem. The problem was that it seems the kernel on detecting this starts killing off seeming random processes, the first one being sshd hence making the machine inaccessible. So the question is: Does the kernel kill random processes when out of swap or does it kill any processes that require more memory when out of swap? Which leads to the question would it not be more sensible to kill off the largest process first as its more than likely that it is responsible for the problem? [quote] Apr 10 20:09:25 appledore kernel: pid 414 (sshd), uid 0, was killed: out of swap space [/quote] Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.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: netstat -m broken.
On Mon, 11 Apr 2005, 12:07-0400, David Gilbert wrote: I'm runing 5.4-STABLE on an dual processor amd64. I'm using the network pretty heavily (dual GigE interfaces doing 300 megabit each) and my netstat -m is giving odd results: FAQ. Documented in 5.3 errata: http://www.freebsd.org/releases/5.3R/errata.html -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Hp dc7100 installs 5.4-rc1 from CD but won't boot from HD
(Which I think covers the problem) Boots from CD ok, USB keyboard seems less than reliable, so I'm using a PS2 item. Running through 'standard' install appears to write data to the (SATA ICH6 controller) disk, but on reboot it sits at the F1: FreeBSD prompt beeping every ten seconds. Is there likely to be anything obvious I've missed? (Or indeed more useful data I can provide.) As a test, I installed a Debian Sarge CD. That works. -- JH-R ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: netstat -m broken.
On Monday 11 April 2005 18:42, Maxim Konovalov wrote: On Mon, 11 Apr 2005, 12:07-0400, David Gilbert wrote: I'm runing 5.4-STABLE on an dual processor amd64. I'm using the network pretty heavily (dual GigE interfaces doing 300 megabit each) and my netstat -m is giving odd results: FAQ. Documented in 5.3 errata: http://www.freebsd.org/releases/5.3R/errata.html Maybe we should add that: $vmstat -z | grep Mbuf gives an idea of the actual memory usage for mbufs. -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpqm9vSn0fiU.pgp Description: PGP signature
Ready for dual core Opterons?
According to the article at http://www.techweb.com/wire/hardware/160503169 AMD is going to be launching dual core Opterons this month. Will FreeBSD 5.4 be ready to handle them? Also, will the nve driver (which is needed to run the Ethernet interface on AMD-based boards with NVidia chipsets) be in 5.4? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ready for dual core Opterons?
Brett Glass wrote: According to the article at http://www.techweb.com/wire/hardware/160503169 AMD is going to be launching dual core Opterons this month. Will FreeBSD 5.4 be ready to handle them? My understanding is that dual core opterons just look like multiple processors to the operating system, so there should be no problems. For that matter, my understanding is that dual core opterons *are* separate processors, connected only via their normal external interface. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ready for dual core Opterons?
On Mon, Apr 11, 2005 at 10:58:50AM -0700, Colin Percival wrote.. Brett Glass wrote: According to the article at http://www.techweb.com/wire/hardware/160503169 AMD is going to be launching dual core Opterons this month. Will FreeBSD 5.4 be ready to handle them? My understanding is that dual core opterons just look like multiple processors to the operating system, so there should be no problems. For that matter, my understanding is that dual core opterons *are* separate processors, connected only via their normal external interface. Ask David (obrien) I suppose. -- 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: two mysterious files in RELENG_5_4
On 4/11/2005 7:24 AM, Rostislav Krasny wrote: Hello all. I have FreeBSD 5.4-RC1 installed from FTP. Today I ran cvsup to get the latest RELENG_5_4 src-all. I've seen two strange files were checkouted by cvsup: Checkout src/installworld_newk Checkout src/installworld_oldk I don't see those files on http://www.freebsd.org/cgi/cvsweb.cgi/src/?only_with_tag=RELENG_5_4 but I see them on http://www.freebsd.org/cgi/cvsweb.cgi/src/Attic/ According to the cvsweb logs those files were removed in HEAD but still exist in RELENG_5_4. But why I don't see them on the cvsweb by the first URL and why they didn't exist in my 5.4-RC1 before cvsup? Or, if they were removed in the RELENG_5_4 too, why cvsup checkouted them today? *sigh* The files were removed from HEAD but still exist in RELENG_5 and children (like RELENG_5_4). What you are experiencing is a limitation of CVSweb: files in the Attic are not handled well (the newest release, 3.0.5, doesn't do this correctly either). I recently started working on CVSweb and this is one of the things on my TODO list. I'm not sure why the 5.4-RC1 src didn't include them; perhaps files are excluded from the src depending on which arch the release is targeting? These particular files are only used for sparc64. Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-S (Mar 6) softdep stack backtrace from getdirtybuf()... problem?
On Apr 11, 2005 3:16 AM, Brandon S. Allbery KF8NH [EMAIL PROTECTED] wrote: I have twice so far had the kernel syslog a stack backtrace with no other information. Inspection of the kernel source, to the best of my limited understanding, suggests that getdirtybuf() was handed a buffer without an associated vnode. Kernel config file and make.conf attached. Should I be concerned? Note that this system is an older 600MHz Athlon with only 256MB RAM, and both times this triggered it was thrashing quite a bit (that's more or less its usual state...). I saw these similar trace on a 5.4-RC1/amd64 with 9 NFS mount. I suspect this is a issue with busy NFS server? rafan. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-S (Mar 6) softdep stack backtrace from getdirtybuf()... problem?
On Tue, 2005-04-12 at 03:29 +0800, Rong-En Fan wrote: I saw these similar trace on a 5.4-RC1/amd64 with 9 NFS mount. I suspect this is a issue with busy NFS server? No, no NFS involved at all, nor any other network filesystem, client or server. -- brandon s. allbery [linux,solaris,freebsd,perl] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineering, carnegie mellon univ. KF8NH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.4-RC2 Available
Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 5.4-RC2, the second Release Candidate of the FreeBSD 5.4 release cycle. We encourage people to help with testing so any final bugs can be identified and worked out. At this point the only major problem has been reports of large server (4 processors or more) hanging under extreme load conditions (varied load of local processes like database and heavy network load). Details to help with debugging have been hard to obtain so if anyone is in a position to help with trying to reproduce this it would be appreciated. Availability of ISO images and support for doing FTP based installs is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_5_4. Problem reports can be submitted using the send-pr(1) command, and/or posted to the freebsd-stable@freebsd.org mailing list. A schedule and the current todo list for the 5.4 Release Cycle are available: http://www.freebsd.org/releases/5.4R/schedule.html http://www.freebsd.org/releases/5.4R/todo.html The packages being provided as part of RC2 are what is expected to come with the final release for the amd64, i386, pc98, and sparc64 architectures. Packages for alpha and ia64 are still being worked on. Availability The RC2 ISOs and FTP support for all architectures are available now on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s of the ISO images are: MD5 (5.4-RC2-alpha-bootonly.iso) = 2238c45b5907931d248487cac55f1c5f MD5 (5.4-RC2-alpha-disc1.iso) = 89ecfdb35ea3cd92716686116b664ea5 MD5 (5.4-RC2-alpha-disc2.iso) = 678581d5b6ae049f18491e203ebadd20 MD5 (5.4-RC2-amd64-bootonly.iso) = 50db1883edf34ff15834da03654d79c3 MD5 (5.4-RC2-amd64-disc1.iso) = a18c728f6259847a1538b03815bfc640 MD5 (5.4-RC2-amd64-disc2.iso) = a0686aa29eca455436f7d9cb0164f055 MD5 (5.4-RC2-i386-bootonly.iso) = 66303d342f235870572b8bd882425445 MD5 (5.4-RC2-i386-disc1.iso) = 08b9ae45f5f6873468d03a3915f55de4 MD5 (5.4-RC2-i386-disc2.iso) = 115fd80bfaa54b94ef194d104e7a803f MD5 (5.4-RC2-ia64-bootonly.iso) = 2e459a193e00f499371252ea98291af4 MD5 (5.4-RC2-ia64-disc1.iso) = 31914a284b740c32e8808e7bfaf408c0 MD5 (5.4-RC2-ia64-disc2.iso) = 875b59e9435ca7e79ab36562cf5c1e88 MD5 (5.4-RC2-ia64-livefs.iso) = 0ae9868c11a46e9f7e56f1e4d71f2e7e MD5 (5.4-RC2-pc98-disc1.iso) = 12f527c1ed165101ff36053c29440212 MD5 (5.4-RC2-sparc64-bootonly.iso) = 6f087402361627a1e6c52c134152c52f MD5 (5.4-RC2-sparc64-disc1.iso) = 411916559bd5ebe03f6ae65622b02e5f MD5 (5.4-RC2-sparc64-disc2.iso) = 1300c0abeda2d00bb859adbc8a1d7a9a -ken pgpZaxXeugqks.pgp Description: PGP signature
Kodak USB flash reader causes freezes, panics
I'm not sure if this should go here or to -bugs, but the other USB-related reports put me in good company, I'm hoping... I'm having a problem with a Kodak USB flash reader. camcontrol inquiry gives me: pass0: Kodak CF/SD/MMC/SM 0108 Removable Direct Access SCSI-0 device pass0: Serial Number pass0: 1.000MB/s transfers The device has printed on it: Kodak Multi-Card Reader CE2A012 KP P/N 7E3771 ITEM# 20209416 P/N 680-070-563 Reproducibly, if I begin copying data to a Lexar 256MB CF card (P/N 2250, Rev. A), it works for a while, then freezes the system. The first time this happened it was when trying to unmount the filesystem. The second time was in the midst of copying data. Both times the system was completely frozen; not even the keyboard LEDs toggled. Strangely, I could connect on the SSH and FTP ports, but received no welcome banner. The third time I modified the script I was using to copy my files to sync and sleep after each file. This time the system seemed to freeze, then lurch through handling several interrupts (mouse pointer moved and a menu popped up from right-clicking), then froze again. Initially connecting to the SSH port brought up the banner after a very long delay, but an attempt to reproduce this was unsuccessful, and I was unable to actually SSH in. Mounting the filesystem synchronously doesn't seem to help. The first time it worked, but then when I unmounted and remounted it and copied some more files it froze midway through. I'm running FreeBSD 5.3: FreeBSD beaker.data-secure.net 5.3-RELEASE-p8 FreeBSD 5.3-RELEASE-p8 #1: Mon Apr 11 15:20:08 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I will be fairly busy for the next few days but later this week I should be able to try out patches or set up a machine running a more cutting-edge source tree, if necessary. I've got FreeBSD 5.4-RC2 building today, actually; is it likely that this will solve my problem? Thanks in advance for any assistance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kodak USB flash reader causes freezes, panics
On Mon, Apr 11, 2005 at 05:24:15PM -0400, Tim Howe wrote: I'm not sure if this should go here or to -bugs, but the other USB-related reports put me in good company, I'm hoping... I'm having a problem with a Kodak USB flash reader. camcontrol inquiry gives me: pass0: Kodak CF/SD/MMC/SM 0108 Removable Direct Access SCSI-0 device pass0: Serial Number pass0: 1.000MB/s transfers The device has printed on it: Kodak Multi-Card Reader CE2A012 KP P/N 7E3771 ITEM# 20209416 P/N 680-070-563 Reproducibly, if I begin copying data to a Lexar 256MB CF card (P/N 2250, Rev. A), it works for a while, then freezes the system. The first time this happened it was when trying to unmount the filesystem. The second time was in the midst of copying data. Both times the system was completely frozen; not even the keyboard LEDs toggled. Strangely, I could connect on the SSH and FTP ports, but received no welcome banner. The third time I modified the script I was using to copy my files to sync and sleep after each file. This time the system seemed to freeze, then lurch through handling several interrupts (mouse pointer moved and a menu popped up from right-clicking), then froze again. Initially connecting to the SSH port brought up the banner after a very long delay, but an attempt to reproduce this was unsuccessful, and I was unable to actually SSH in. Mounting the filesystem synchronously doesn't seem to help. The first time it worked, but then when I unmounted and remounted it and copied some more files it froze midway through. I'm running FreeBSD 5.3: FreeBSD beaker.data-secure.net 5.3-RELEASE-p8 FreeBSD 5.3-RELEASE-p8 #1: Mon Apr 11 15:20:08 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I will be fairly busy for the next few days but later this week I should be able to try out patches or set up a machine running a more cutting-edge source tree, if necessary. I've got FreeBSD 5.4-RC2 building today, actually; is it likely that this will solve my problem? It is quite likely that 5.4 fixed your problem. Not certain, of course, but many problems have been fixed recently. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpEl9k3d1gNq.pgp Description: PGP signature
Intel 6300ESB (ICH) SMBus controller not working
Hi, I'm running RELENG_5 on a Dell PowerEdge 750 and the ichsmb driver doesn't want to work with it, I get the following on boot: ichsmb0: Intel 6300ESB (ICH) SMBus controller port 0x8c0-0x8df irq 17 at device 31.3 on pci0 device_attach: ichsmb0 attach returned 6 It then doesn't load smb or smbus. I had a look in the source and it is supposed to work with this controller. Is this something wrong with the driver? or have I left out some bit of configuration? Attached is the output from boot -v and my kernel configuration. Is there any other debugging output that would be useful? Cheers, Phil -- include GENERIC ident ALEXIS options HZ=1000 options MAXDSIZ=(1024*1024*1024) options MAXSSIZ=(1024*1024*1024) options DFLDSIZ=(1024*1024*1024) options SEMMNI=256 options SEMMNS=512 options SEMMNU=256 options SEMMAP=256 options SHMMAXPGS=4096 options ACCEPT_FILTER_HTTP device smb device smbus device ichsmb device iic device iicbus device iicbb device iicsmb device usb device uhci device ehci /boot/kernel/acpi.ko text=0x41480 data=0x1da4+0x112c syms=[0x4+0x7630+0x4+0x9c97] SMAP type=01 base= len=000a SMAP type=01 base=0010 len=7fec SMAP type=02 base=7ffcfc00 len=0400 SMAP type=03 base=7ffc len=fc00 SMAP type=02 base=7ffd len=0002 SMAP type=02 base=7fff len=f000 SMAP type=02 base=fed2 len=0006 SMAP type=02 base=fec0 len=0009 SMAP type=02 base=fee0 len=0001 SMAP type=02 base=ffb0 len=0050 Copyright (c) 1992-2005 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 5.4-STABLE #4: Mon Apr 11 12:24:01 NZST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALEXIS Preloaded elf kernel /boot/kernel/kernel at 0xc0a45000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0a4526c. Calibrating clock(s) ... i8254 clock: 1193174 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3400136841 Hz CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (3400.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 2147221504 (2047 MB) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x7db90fff, 2096545792 bytes (511852 pages) avail memory = 2095755264 (1998 MB) Table 'FACP' at 0xfdc84 Table 'APIC' at 0xfdcf8 MADT: Found table at 0xfdcf8 MP Configuration Table version 1.4 found at 0xc00f APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled MADT: Found CPU APIC ID 1 ACPI ID 2: enabled ACPI APIC Table: DELL PE750 bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xc9de pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f:e2f4 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 1 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0 ioapic0: Changing APIC ID to 2 ioapic0: Routing external 8259A's - intpin 0 ioapic0: intpin 0 - ExtINT (edge, high) ioapic0: intpin 1 - ISA IRQ 1 (edge, high) ioapic0: intpin 2 - ISA IRQ 2 (edge, high) ioapic0: intpin 3 - ISA IRQ 3 (edge, high) ioapic0: intpin 4 - ISA IRQ 4 (edge, high) ioapic0: intpin 5 - ISA IRQ 5 (edge, high) ioapic0: intpin 6 - ISA IRQ 6 (edge, high) ioapic0: intpin 7 - ISA IRQ 7 (edge, high) ioapic0: intpin 8 - ISA IRQ 8 (edge, high) ioapic0: intpin 9 - ISA IRQ 9 (edge, high) ioapic0: intpin 10 - ISA IRQ 10 (edge, high) ioapic0: intpin 11 - ISA IRQ 11 (edge, high) ioapic0: intpin 12 - ISA IRQ 12 (edge, high) ioapic0: intpin 13 - ISA IRQ 13 (edge, high) ioapic0: intpin 14 - ISA IRQ 14 (edge, high) ioapic0: intpin 15 - ISA IRQ 15 (edge, high) ioapic0: intpin 16 - PCI IRQ 16 (level, low) ioapic0: intpin 17 - PCI IRQ 17 (level, low) ioapic0: intpin 18 - PCI IRQ 18 (level, low) ioapic0: intpin 19 - PCI IRQ 19 (level, low) ioapic0: intpin 20 - PCI IRQ 20 (level, low) ioapic0: intpin 21 - PCI IRQ 21 (level, low) ioapic0: intpin 22 - PCI IRQ 22 (level, low) ioapic0: intpin 23 - PCI IRQ 23 (level, low) MADT: Found IO APIC ID 3, Interrupt 24 at 0xfec1 ioapic1: Changing APIC ID to 3 ioapic1: intpin 0 - PCI IRQ 24 (level, low) ioapic1: intpin 1 - PCI IRQ 25 (level, low) ioapic1: intpin 2 - PCI IRQ 26 (level, low) ioapic1: intpin 3 - PCI IRQ 27 (level, low) ioapic1: intpin 4 - PCI IRQ 28 (level, low) ioapic1: intpin 5 - PCI IRQ 29 (level,
SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze
Greetings, We have a SuperMicro X5DP8-G2 Motherboard, 2xXEON 2.4, 1GB RAM server running 5.4-STABLE that keeps freezing up. We have replaced RAM, HD, SCSI controller, etc. To no avail. We are running SMP GENERIC Kernel. I cannot get the system to panic, leave a core dump, etc. It just always freezes. The server functions as a web server in a HSphere Cluster. I am about out of options besides loading 4.11 (since our 4 series servers never die). Any help, feedback, clues, similar experiences, etc would be greatly appreciated. On SCSI: The onboard Adaptec 7902 gives a dump on bootup but appears to work. I read the archived post about this issue. The system still locked up with an Adaptec 7982B that did not give this message. DMESG: Copyright (c) 1992-2005 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 5.4-STABLE #2: Sat Apr 9 09:16:44 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 1073217536 (1023 MB) avail memory = 1040605184 (992 MB) 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 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic3 Version 2.0 irqs 72-95 on motherboard ioapic4 Version 2.0 irqs 96-119 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 cpu1: ACPI CPU (2 Cx states) on acpi0 cpu2: ACPI CPU (2 Cx states) on acpi0 cpu3: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 29.0 on pci1 pci2: ACPI PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 31.0 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3000-0x303f mem 0xfc20-0xfc21 irq 28 at device 2.0 on pci3 em0: Ethernet address: 00:30:48:2d:0a:2c em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3040-0x307f mem 0xfc22-0xfc23 irq 29 at device 2.1 on pci3 em1: Ethernet address: 00:30:48:2d:0a:2d em1: Speed:N/A Duplex:N/A pcib4: ACPI PCI-PCI bridge at device 3.0 on pci0 pci4: ACPI PCI bus on pcib4 pci4: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib5: ACPI PCI-PCI bridge at device 29.0 on pci4 pci5: ACPI PCI bus on pcib5 pci4: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib6: ACPI PCI-PCI bridge at device 31.0 on pci4 pci6: ACPI PCI bus on pcib6 ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4000-0x40ff,0x4400-0x44ff mem 0xfc40-0xfc401fff irq 76 at device 2.0 on pci6 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc402000-0xfc403fff irq 77 at device 2.1 on pci6 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x2000-0x201f irq 16 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x2020-0x203f irq 19 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x2040-0x205f irq 18 at device 29.2 on pci0 usb2: Intel 82801CA/CAM (ICH3) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib7: ACPI PCI-PCI bridge at device 30.0 on pci0 pci7: ACPI PCI bus on pcib7 pci7: display, VGA at device 1.0 (no
Re: Kodak USB flash reader causes freezes, panics
Brooks Davis [EMAIL PROTECTED] writes: On Mon, Apr 11, 2005 at 05:24:15PM -0400, Tim Howe wrote: Reproducibly, if I begin copying data to a [...] CF card [...] it works for a while, then freezes the system. It is quite likely that 5.4 fixed your problem. Unfortunately not. I was able, having mounted the filesystem with no synchronization options, to copy 171MiB of data onto it and unmount. However when I re-mounted it with the same options and tried to copy 71MiB more, it again froze midway through. Everything else (X11, sound, printing, input) seems to be working perfectly with 5.4, but I did notice something new and strange with regard to umass. I still have to run true /dev/da0 to get the slice to show up, but now I get the following: [1042] ~ # true /dev/da0 [1043] ~ # camcontrol rescan 0 Re-scan of bus 0 was successful [1044] ~ # ls -l /dev/da0* crw-r- 1 root operator4, 21 Apr 11 21:45 /dev/da0 crw-r- 1 root operator4, 28 Apr 11 21:45 /dev/da0s1 crw-r- 1 root operator4, 29 Apr 11 21:45 /dev/da0s1s1 [1045] ~ # mount_msdosfs /dev/da0s1 /mnt/cf [1046] ~ # umount /mnt/cf [1047] ~ # mount_msdosfs /dev/da0s1s1 /mnt/cf [1048] ~ # umount /mnt/cf Thoughts? FreeBSD beaker.data-secure.net 5.4-RC2 FreeBSD 5.4-RC2 #2: Mon Apr 11 20:31:53 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze
Aaron Summers presumably uttered the following on 04/11/05 22:12: Greetings, We have a SuperMicro X5DP8-G2 Motherboard, 2xXEON 2.4, 1GB RAM server running 5.4-STABLE that keeps freezing up. We have replaced RAM, HD, SCSI controller, etc. To no avail. We are running SMP GENERIC Kernel. I cannot get the system to panic, leave a core dump, etc. It just always freezes. The server functions as a web server in a HSphere Cluster. I am about out of options besides loading 4.11 (since our 4 series servers never die). Any help, feedback, clues, similar experiences, etc would be greatly appreciated. On SCSI: The onboard Adaptec 7902 gives a dump on bootup but appears to work. I read the archived post about this issue. The system still locked up with an Adaptec 7982B that did not give this message. DMESG: snip da2 at ahd0 bus 0 target 4 lun 0 da2: SEAGATE ST336607LC 0007 Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST336754LC 0002 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da1 at ahd0 bus 0 target 2 lun 0 da1: SEAGATE ST336754LC 0002 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) Mounting root from ufs:/dev/da0s1a We had many issues with Seagate drives and and S/M boards with the onboard Adaptec scsi controllers. Seagate offered no help other than to suggest putting in a network card (in lieu of the onboard) and/or disabling SMP; neither solution was acceptable so we switched to IBM/Hitachi drives and the problems disappeared. By the way, the problems manifested themselves in those servers where we had more than just one hard drive installed. This was even after updating to the latest firmware etc; Seagate insists no problem with their drives although other drives work perfectly well. YMMV I do see you say you tried other harddrives .. which ones did you use? Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 6300ESB (ICH) SMBus controller not working
At 09:24 PM 11/04/2005, Philip Murray wrote: Hi, I'm running RELENG_5 on a Dell PowerEdge 750 and the ichsmb driver doesn't want to work with it, I get the following on boot: ichsmb0: Intel 6300ESB (ICH) SMBus controller port 0x8c0-0x8df irq 17 at device 31.3 on pci0 device_attach: ichsmb0 attach returned 6 Does it work if you add debug.acpi.disabled=sysresource to /boot/loader.conf ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] Stability fixes for IPS driver for 4.x
At 11:31 PM 10/04/2005 -0600, Scott Long wrote this to All: Making a driver PAE-ified means either teaching it to do 64-bit scatter-gather (assuming that the peripheral hardware can do this and that it's documented), or teaching the driver to correctly handle EINPROGRESS from bus_dmamap_load() along with using the proper busdma tag limits. The strategy I took with 6.x/5.x was the second one since I didn't have good IPS docs in front of me and I wanted it follow the APIs correctly. I did test it with 8GB of memory and it performed correctly under load. I haven't taken a close enough look at your MFC patch to say for sure if it's correct or not. I'm not sure if I'll have time to take another look in the next few days, unfortunately. Is there any chance you could test 5.x/6.0 under load with PAE just to validate the assertion that it works correctly there? I had a chance to test 5.4-RC1 (i386) today with GENERIC, SMP, PAE, and SMP-PAE kernels (the last one is just PAE with options SMP). To recap, the hardware is an IBM xSeries 346, Dual Xeon 3GHz (non-E64MT), ServeRAID-7K. GENERIC and SMP survived make buildkernel, but PAE and SMP-PAE paniced reproducibly doing the same. The DDB stack trace doesn't appear to be anywhere near the IPS driver though, so I'm way out of my league. == PAE panic 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 = 0x8:0xc03d48eb stack pointer = 0x10:0xeb133b28 frame pointer = 0x10:0xeb133b3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 146 (syncer) [thread pid 146 tid 100157 ] Stopped at propagate_priority+0x7f: movl0x24(%eax),%eax db trace Tracing pid 146 tid 100157 td 0xc68cba80 propagate_priority turnstile_wait _mtx_lock_sleep vfs_clean_pages bdwrite ffs_blkfree handle_workitem_freefrag process_worklist_item softdep_process_worklist sched_sync fork_exit fork_trampoline --- trap 0x1, eip = 0, esp = 0xeb133d7c, ebp = 0 --- == End PAE panic == SMP-PAE panic kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc03d7cd3 stack pointer = 0x10:0xeb0d0b7c frame pointer = 0x10:0xeb0d0b90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 149 (syncer) [thread pid 149 tid 100160 ] Stopped at propagate_priority+0x7f: movl0x24(%eax),%eax db trace Tracing pid 149 tid 100160 td 0xc68b2000 propagate_priority turnstile_wait _mtx_lock_sleep vfs_busy_pages ibwrite bwrite vfs_bio_awrite vop_stdfsync spec_fsync spec_vnoperate sched_sync fork_exit fork_trampoline --- trap 0x1, eip = 0, esp = 0xeb0d0d7c, ebp = 0 --- == End PAE panic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze
Hi, I had exactly the same issue with a X5DPR-iG2+ Supermicro motherboard, but solved it after just disabling Power Mgmt and Hyperthreading in the BIOS. In my case, it had nothing to do with the FreeBSD version or kernel , the machine was freezing couple of times a week during months with different 4.x and 5.x stable versions. -Carlos - Original Message - From: Aaron Summers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, April 11, 2005 11:12 PM Subject: SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze Greetings, We have a SuperMicro X5DP8-G2 Motherboard, 2xXEON 2.4, 1GB RAM server running 5.4-STABLE that keeps freezing up. We have replaced RAM, HD, SCSI controller, etc. To no avail. We are running SMP GENERIC Kernel. I cannot get the system to panic, leave a core dump, etc. It just always freezes. The server functions as a web server in a HSphere Cluster. I am about out of options besides loading 4.11 (since our 4 series servers never die). Any help, feedback, clues, similar experiences, etc would be greatly appreciated. On SCSI: The onboard Adaptec 7902 gives a dump on bootup but appears to work. I read the archived post about this issue. The system still locked up with an Adaptec 7982B that did not give this message. DMESG: Copyright (c) 1992-2005 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 5.4-STABLE #2: Sat Apr 9 09:16:44 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 1073217536 (1023 MB) avail memory = 1040605184 (992 MB) 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 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic3 Version 2.0 irqs 72-95 on motherboard ioapic4 Version 2.0 irqs 96-119 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 cpu1: ACPI CPU (2 Cx states) on acpi0 cpu2: ACPI CPU (2 Cx states) on acpi0 cpu3: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 29.0 on pci1 pci2: ACPI PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 31.0 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3000-0x303f mem 0xfc20-0xfc21 irq 28 at device 2.0 on pci3 em0: Ethernet address: 00:30:48:2d:0a:2c em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3040-0x307f mem 0xfc22-0xfc23 irq 29 at device 2.1 on pci3 em1: Ethernet address: 00:30:48:2d:0a:2d em1: Speed:N/A Duplex:N/A pcib4: ACPI PCI-PCI bridge at device 3.0 on pci0 pci4: ACPI PCI bus on pcib4 pci4: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib5: ACPI PCI-PCI bridge at device 29.0 on pci4 pci5: ACPI PCI bus on pcib5 pci4: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib6: ACPI PCI-PCI bridge at device 31.0 on pci4 pci6: ACPI PCI bus on pcib6 ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4000-0x40ff,0x4400-0x44ff mem 0xfc40-0xfc401fff irq 76 at device 2.0 on pci6 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc402000-0xfc403fff irq 77 at device 2.1 on pci6 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x2000-0x201f irq 16 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x2020-0x203f irq 19 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1:
Re: Intel 6300ESB (ICH) SMBus controller not working
On 12/04/2005, at 2:38 PM, Mike Tancsa wrote: At 09:24 PM 11/04/2005, Philip Murray wrote: Hi, I'm running RELENG_5 on a Dell PowerEdge 750 and the ichsmb driver doesn't want to work with it, I get the following on boot: ichsmb0: Intel 6300ESB (ICH) SMBus controller port 0x8c0-0x8df irq 17 at device 31.3 on pci0 device_attach: ichsmb0 attach returned 6 Does it work if you add debug.acpi.disabled=sysresource to /boot/loader.conf Thanks for that, It kind of worked. Am I correct in thinking that, that prevents ACPI attaching to the controller so that the ichsmb driver can? In which case, if ACPI does attach to it, does that mean I'd get temperature values in the hw.acpi.thermal tree? sysutils/xmbmon and sysutils/healthd can't seem to read anything from it anyway. Is this because the SMBus has no temperature sensors tied to it? It has them in the BIOS, so I assumed I could read them in FreeBSD. I get ichsmb0: irq 0x04 during -1 in dmesg when trying healthd and [EMAIL PROTECTED]:~/ healthd -S ioctl(SMB_WRITEB): Permission denied Cheers, Phil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
