alpm0: Could not allocate Bus space
I'm trying to resurrect an Asus P5A-B system and the power management is failing. The relevant parts of the dmesg are: FreeBSD 5.3-RELEASE-p5 #2: Sat Mar 5 21:54:19 EST 2005 ... bios32: Found BIOS32 Service Directory header at 0xc00f9b80 bios32: Entry = 0xf0530 (c00f0530) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x560 pnpbios: Found PnP BIOS data at 0xc00fcfb0 pnpbios: Entry = f:cfe0 Rev = 1.0 pnpbios: OEM ID cd041 acpi0: ASUS P5A-B on motherboard acpi0: [MPSAFE] ... found- vendor=0x10b9, dev=0x7101, revid=0x00 bus=0, slot=3, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) ... alpm0: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0 alpm0: host/noslave 74K alpm0: 0x20 bytes of rid 0x14 res 4 failed. alpm0: Could not allocate Bus space device_attach: alpm0 attach returned 6 I've had a look through the archives but not been able to find this problem. Has anyone else seen it and how would I go about fixing it? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: patch: fix ata panic with Thinkpad CD and DVD drives
Nate Lawson wrote: If you've been having memory modified after free panics on -current and have a Thinkpad, the attached patch should fix things for you. A quick check of RELENG_5 indicates that the bug is probably there also but I haven't tested for it there. The bug is triggered by timeouts in the ata_getparam() probe path. The ata_timeout() fires and ata_end_transaction() is called to get the status. However, it continues down into ata_pio_read() even though there is no data available since we had a timeout, not read completion. ata_pio_read() reads 512 bytes of probably bogus data. The important problem is that it also advances donecount. On subsequent timeouts (note there are 4 below), donecount advances into unallocated memory and so subsequent ata_pio_read() calls overwrite 512 bytes of someone else's memory. The fix is to exit immediately if ATA_R_TIMEOUT is set after reading the status in ata_end_transaction(). It shouldn't go into ata_pio_read() if there was a timeout. The patch does this. However, it only handles PIO timeouts since I wasn't sure the best way to proceed for unwinding DMA state and the like for the other cases. This is enough to fix the overwrite and subsequent panic on my systems. I've run heavy IO stress and DVD accesses for a while and no further panics. While looking into this, I found another potential problem. In one reinjection case, donecount wasn't reset to 0. The patch for ata-queue.c does this and I think it's necessary but don't hit this case in testing so I can't be sure. Finally, there's one whitespace nit that helps with clarity. These are similar bugs to one found back in August that had the same effect. Here's the closest reference I could find in the mail archives for this: http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-August/033033.html Just a note from here, these bugs are fixed in ATA mkIII so you could just have gleaned the solution from there (or maybe you did :)) -- -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-RELEASE (amd64) on LSILogic 1030 / mpt controller.
Hello, I'm trying, without success, to install the FreeBSD 5.3 on a Sun Fire V40z (it's an amd64 box) on its LSILogic 1030 Ultra4 SCSI controller. It goes well, the kernel detects disks properly, creates the partitions, but dies after trying to copy files to /stand. [...] mpt0: time out in request index=0xf8 sequence=0x03a3 mpt0: Statys 0001; Mask 0001; Doorbell 2400 request state On Chip SCSI IO Request @ 0x67652ae0 Chain Offset0x00 MsgFlags0x00 MsgContext 0x00ed Bus:0 TargetID0 SenseBufferLength 32 LUN:0x0 Control 0x0100 WRITE SIMPLEQ DataLength 0x0800 SenseBufAddr0xe3f3bbe0 CDB[0:6]0a 02 00 6b 04 00 SE32 0x68040c30: Addr=0xc62c0800 FlagsLength=0xd5000800 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST [...] The output is copied by hand, so there can be some small typos, even though I tried to recheck it ;) ACPI, no ACPI and Safe mode make no difference, installation dies in the same place. Anyone any ideas? PS, cross-posted to freebsd-amd64. Regards, -- Krzysztof Kowalik | () ASCII Ribbon Campaign Computer Center, AGH UST| /\ Support plain text e-mail ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Just a sanity check before I sumbit a buig report
The man page for getrusage says that the frequency of the statistics
clock is given by sysconf(_SC_CLK_TCK).
The source code to /usr/bin/time uses a function 'getstathz' to get
the frequency of the statistics clock which is does using sysctl
and KERN_CLOCKRATE
On my system the first returns 100Hz and the second 128Hz!!!
Now, is this:
1) A bug in /usr/bin/time
2) A bug in sysconf(_SC_CLK_TCK)
3) A bug in the manpage for getrusage
4) A bug in the kernel and the values should not be different
5) A bug in my understanding!
Note that although option '4' is unlikely, if I run the test a.out file
on other FreeBSD systems I get 128 for both values, which is even odder!
-pcf.
Test code (will probably give 128 for both on your system)
#include stdio.h
#include unistd.h
#include err.h
#include sys/types.h
#include sys/time.h
#include sys/sysctl.h
static int
getstathz()
{
struct clockinfo clockrate;
int mib[2];
size_t size;
mib[0] = CTL_KERN;
mib[1] = KERN_CLOCKRATE;
size = sizeof clockrate;
if (sysctl(mib, 2, clockrate, size, NULL, 0) == -1)
err(1, sysctl kern.clockrate);
return clockrate.stathz;
}
int
main()
{
printf(get stat hz = %d\n, getstathz());
printf(sysconf clock tick = %ld\n, sysconf(_SC_CLK_TCK));
return 0;
}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: patch: fix ata panic with Thinkpad CD and DVD drives
Søren Schmidt wrote: Nate Lawson wrote: If you've been having memory modified after free panics on -current and have a Thinkpad, the attached patch should fix things for you. A quick check of RELENG_5 indicates that the bug is probably there also but I haven't tested for it there. The bug is triggered by timeouts in the ata_getparam() probe path. The ata_timeout() fires and ata_end_transaction() is called to get the status. However, it continues down into ata_pio_read() even though there is no data available since we had a timeout, not read completion.ata_pio_read() reads 512 bytes of probably bogus data. The important problem is that it also advances donecount. On subsequent timeouts (note there are 4 below), donecount advances into unallocated memory and so subsequent ata_pio_read() calls overwrite 512 bytes of someone else's memory. The fix is to exit immediately if ATA_R_TIMEOUT is set after reading the status in ata_end_transaction(). It shouldn't go into ata_pio_read() if there was a timeout. The patch does this. However, it only handles PIO timeouts since I wasn't sure the best way to proceed for unwinding DMA state and the like for the other cases. This is enough to fix the overwrite and subsequent panic on my systems. I've run heavy IO stress and DVD accesses for a while and no further panics. While looking into this, I found another potential problem. In one reinjection case, donecount wasn't reset to 0. The patch for ata-queue.c does this and I think it's necessary but don't hit this case in testing so I can't be sure. Finally, there's one whitespace nit that helps with clarity. These are similar bugs to one found back in August that had the same effect. Here's the closest reference I could find in the mail archives for this: http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-August/033033.html Just a note from here, these bugs are fixed in ATA mkIII so you could just have gleaned the solution from there (or maybe you did :)) Nope, but I'm glad you can corroborate these fixes are correct. -- Nate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: patch: fix ata panic with Thinkpad CD and DVD drives
Søren Schmidt wrote: Nate Lawson wrote: If you've been having memory modified after free panics on -current and have a Thinkpad, the attached patch should fix things for you. A quick check of RELENG_5 indicates that the bug is probably there also but I haven't tested for it there. The bug is triggered by timeouts in the ata_getparam() probe path. The ata_timeout() fires and ata_end_transaction() is called to get the status. However, it continues down into ata_pio_read() even though there is no data available since we had a timeout, not read completion.ata_pio_read() reads 512 bytes of probably bogus data. The important problem is that it also advances donecount. On subsequent timeouts (note there are 4 below), donecount advances into unallocated memory and so subsequent ata_pio_read() calls overwrite 512 bytes of someone else's memory. The fix is to exit immediately if ATA_R_TIMEOUT is set after reading the status in ata_end_transaction(). It shouldn't go into ata_pio_read() if there was a timeout. The patch does this. However, it only handles PIO timeouts since I wasn't sure the best way to proceed for unwinding DMA state and the like for the other cases. This is enough to fix the overwrite and subsequent panic on my systems. I've run heavy IO stress and DVD accesses for a while and no further panics. While looking into this, I found another potential problem. In one reinjection case, donecount wasn't reset to 0. The patch for ata-queue.c does this and I think it's necessary but don't hit this case in testing so I can't be sure. Finally, there's one whitespace nit that helps with clarity. These are similar bugs to one found back in August that had the same effect. Here's the closest reference I could find in the mail archives for this: http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-August/033033.html Just a note from here, these bugs are fixed in ATA mkIII so you could just have gleaned the solution from there (or maybe you did :)) Nope, but I'm glad you can corroborate these fixes are correct. -- Nate ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: patch: fix ata panic with Thinkpad CD and DVD drives
Nate Lawson wrote: Søren Schmidt wrote: Nate Lawson wrote: If you've been having memory modified after free panics on -current and have a Thinkpad, the attached patch should fix things for you. A quick check of RELENG_5 indicates that the bug is probably there also but I haven't tested for it there. The bug is triggered by timeouts in the ata_getparam() probe path. The ata_timeout() fires and ata_end_transaction() is called to get the status. However, it continues down into ata_pio_read() even though there is no data available since we had a timeout, not read completion.ata_pio_read() reads 512 bytes of probably bogus data. The important problem is that it also advances donecount. On subsequent timeouts (note there are 4 below), donecount advances into unallocated memory and so subsequent ata_pio_read() calls overwrite 512 bytes of someone else's memory. The fix is to exit immediately if ATA_R_TIMEOUT is set after reading the status in ata_end_transaction(). It shouldn't go into ata_pio_read() if there was a timeout. The patch does this. However, it only handles PIO timeouts since I wasn't sure the best way to proceed for unwinding DMA state and the like for the other cases. This is enough to fix the overwrite and subsequent panic on my systems. I've run heavy IO stress and DVD accesses for a while and no further panics. While looking into this, I found another potential problem. In one reinjection case, donecount wasn't reset to 0. The patch for ata-queue.c does this and I think it's necessary but don't hit this case in testing so I can't be sure. Finally, there's one whitespace nit that helps with clarity. These are similar bugs to one found back in August that had the same effect. Here's the closest reference I could find in the mail archives for this: http://lists.freebsd.org/mailman/htdig/freebsd-current/2004-August/033033.html Just a note from here, these bugs are fixed in ATA mkIII so you could just have gleaned the solution from there (or maybe you did :)) Nope, but I'm glad you can corroborate these fixes are correct. Actually I cant, I havn't looked at what was committed since I already did fix these problems in the mkIII patches floating around.. Anyhow its in there and the committer has to deal with it until/if I commit mkIII to -current, I'm out of the loop until then... -- -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible problems with Broadcom BCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin Operteron
On Mar 4, 2005, at 7:56 AM, Alan Jay wrote: We switched off the broadcom Ethernet controller (via software) and routed all traffic via the boards Intel 10/000 Ethernet connection. One of the problem databases has now been running for a few days and so far has been ok. FWIW, I have a dual opteron tyan 2881 board with 4GB and the same NIC chip (as identified by FreeBSD 5-STABLE). No problems under pretty decent load. Perhaps it has to do also with 4Gb RAM. Could you test that theory too? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can FreeBSD 5.3R support the RAID card MegaRAID SCSI 320-2E
On Mar 5, 2005, at 7:46 AM, Alan Jay wrote: We use these RAID controllers on our machines and have been running the 320-1 and 320-2 with 4.10 very happily and without incident. We have also been running the 320-1 on 5.3 -STABLE and although we have had problems with 5.3 it hasn't had anything to do with the RAID controller :). Add the 320-2X card (AMD64 FreeBSD 5-STABLE, Dual Opteron 4GB RAM). Incredibly fast and stable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can FreeBSD 5.3R support the RAID card MegaRAID SCSI 320-2E card?
On Mar 6, 2005, at 4:11 AM, Aristedes Maniatis wrote: On 05/03/2005, at 7:00 PM, Doug White wrote: The amr(4) manpage in -CURRENT lists the 320 variants, the -2E specifically (is that a PCI Express version?). We have a amr(4) driver update coming in shortly to -CURRENT and then RELENG_5; keep an eye out for that and test it if you can. * will that update make it into 5.4? * what is the nature of the update? Is it primarily for bug fixes or performance improvements? Is it an important update for someone running a production machine with amr (like us) on 5.3? All good questions I'm interested in too. I have a box scheduled for delivery late next week which is a dual opteron with the 320-2X card in it. I can hold it from production for a week or so for such testing. Hopefully the scheduling of the MFC will coincide with this timeframe :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error buildworld
On Sat, 5 Mar 2005, Admin @ InterCorner wrote: Hi, I have installed FreeBSD 5.3 and made a CVSup with the RELENG_5_3 tag. Now when I run # make buildworld I get several errors, and the compiling stops. Here is the error from the i686 build: /usr/src/gnu/usr.bin/binutils/as/../../../../contrib/binutils/gas/listing.c:1264 : internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. This is usually indicative of hardware problems, such as insufficient cooling or bad memory. Check your environmentals. For the full log of the complie go to this url: http://intercorner.net/buildworld-k7.log (1MB) http://intercorner.net/buildworld-i686.log (400kb) (The files will be online for two weeks from now) If you need any other outputs, just tell me! I should also say I couldn't make cvsup-without-gui from ports on this box, so I had to use pkg_add to get it to work.. :/ This really sounds like your system has issues. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
consistent problem with pcm0 audio
Hello, I am using FreeBSD 5-STABLE from Feb 23rd with an onboard VIA VT8237/Avance Logic ALC200 sound controller. Periodically, sound will stop working. I will get the last note (sound packet?) repeated over and over until I close the program. Any further attempt to play a sound will cause the same note to be repeated. I am not able to reload the driver. Correct sound is restored when I reboot the computer. This has been happening for awhile and I am not certain if it was introduced with any particular update. I am using ACPI. I don't know if this also happens without ACPI. I also get a message on the console like this when the error occurs: pcm0:play:0: play interrupt timeout, channel dead uname: FreeBSD tyr.housing.ufl.edu 5.3-STABLE FreeBSD 5.3-STABLE #2: Wed Feb 23 18:53:5 7 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/kernel amd64 pciconf: [EMAIL PROTECTED]:17:5: class=0x040100 card=0x13001462 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class= multimedia subclass = audio -Will -- Will Saxon Systems Programmer, Network Services University of Florida Department of Housing (352) 392-2171 x10148 [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: Error with CMD 649 ATA100 controller while copying files over NFS on 4.11-Stable
On Sat, 5 Mar 2005, Eric Buchanan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I switched one hard drive to a CMD 649 ATA100 controller last summer, and I've had some trouble with it on 4.11-Stable. When I copy a large volume of files over NFS (800 Megabytes, lets say) the add on controller will stop recognizing my hard drive. This time the files were not being copied off a drive handled by this controller. Any ideas? This only occurs when copying files over nfs, and it will happen even when I am not copying anything involving the drive on the controller. I've tried atacontrol reinit 2 and it won't re-recognize the hard drive (ad5s4f). I have absolutely zero problems when I am not using NFS, especially zero problems with make worlds or building large ports on this hard drive in question. the CMD controller chips are known to be poor quality, you may be better off switching to a different controller. And change the cables out while you're at it. The messages below indicate that the drive itself is getting confused and ceasing to respond, but its hard to tell. ad5: 57241MB OEM60-54A 60GB 5400RPM [116301/16/63] at ata2-slave UDMA100 What brand/model is this drive, actually? It looks like its lost its identity data. ad5s4f: soft error (ECC corrected) reading fsbn 185641109 of 84275072-84275075 ( ad5s4 bn 185641109; cn 11555 tn 159 sn 17)ad5s4f: hard error reading fsbn 185641 109 of 84275072-84275075 (ad5s4 bn 185641109; cn 11555 tn 159 sn 17) trying PIO mode ad5: READ command timeout tag=0 serv=0 - resetting ata2: resetting devices .. ad5: removed from configuration done -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-Stable Dual Opteron with 12GB memory!
Anybody running a recent 5.3-stable amd64 on a box with lots of memory, and does it work? From very brief testing a Dual Opteron with 12GB memory just reboots when the kenel probes devices. SATA disks on built in SiL 3114 controller. 5.3-stable from yesterday compiled with -O, the system works with 8GB memory. Have anybody else got a similar system working? /Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Promise FastTrak Tx4200 FreeBSD 5.3
Hi folks Anyone have any ideas on the Promise PDC20319 (Fasttrak S150 TX4)? We intend to run 5.3 release on this machine. Thanks! Simon Litchfield. -- Quo Consulting [EMAIL PROTECTED] http://www.quo.com.au/ Phone +61 (0)7 5520 2665 Fax +61 (0)2 8569 2377 Level 3 : Old Burleigh Theatre Arcade 66 Goodwin Terrace : Burleigh Heads Queensland : Australia ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can FreeBSD be installed on DellPowerEdge2800 ?
On Wed, Mar 02, 2005 at 08:25:40AM -0600, Art Mason wrote:
Vinny Abello wrote:
At 05:50 PM 3/1/2005, Art Mason wrote:
Indeed, just installed on a customer's server last night, and I build
SMP support into the GENERIC kernel this morning. Only issues I
encountered has to do w/ recognizing the full 4GB of RAM, but this
apparently has some compatibility issues w/ the amr driver.
As per Holger's comments about disabling USB in BIOS, this is a good
suggestion, since the DRAC apparently causes some IRQ issues w/ the
PS/2 keyboard controller, or something along those lines. Regardless,
these 2850 boxes are stupid fast, and I'm looking forward to
benchmarking 5.3 on them.
FYI, the architecture of the 2850 (assuming it is similar to your 2800)
requires that you enable PAE support in your kernel of whatever OS you
run to address the full 4GB of RAM. This is due in some part because of
the memory mapping that was done for the PCI express bus and/or onboard
Perc controller (per Dell tech support). We've run into this with all of
our 2850's with various OS's and enabling PAE (per Dell's advice) fixes it.
Yeah, I cam across that on some mailing list archives, but saw some
additional references that this can cause issues with the amr driver.
Have you experienced any instability issues with the amr driver and PAE
enabled? If not, then I'll give this a shot on one of our lab boxes for
testing. Thanks for the suggestion, BTW.
On my 2850 the upper 1GB of RAM cannot be addressed without PAE support
in the kernel. However, amr in 4.11-RELEASE does indeed seem to have
trouble with PAE. The result being that with the option in the kernel,
the root device (ufs:/dev/amrd0s1a) cannot be found.
I backported scottl's amr PAE fixes from RELENG_5; the diffs applied
cleanly (with offsets). I'm happy to report that my 2850 can now
address its full 4GB and see its amr volumes.
The diff against 4.11-RELEASE is attached, hopefully someone will be
willing to commit it to RELENG_4.
*** sys/dev/amr/amr.c.orig Thu Jul 22 09:35:18 2004
--- sys/dev/amr/amr.c Tue Mar 8 15:11:33 2005
***
*** 132,143
* Command processing.
*/
static intamr_bio_command(struct amr_softc *sc, struct amr_command **acp);
! static intamr_wait_command(struct amr_command *ac);
static intamr_getslot(struct amr_command *ac);
! static void amr_mapcmd(struct amr_command *ac);
static void amr_unmapcmd(struct amr_command *ac);
static intamr_start(struct amr_command *ac);
static void amr_complete(void *context, int pending);
/*
* Status monitoring
--- 132,146
* Command processing.
*/
static intamr_bio_command(struct amr_softc *sc, struct amr_command **acp);
! static intamr_wait_command(struct amr_command *ac) __unused;
static intamr_getslot(struct amr_command *ac);
! static intamr_mapcmd(struct amr_command *ac);
static void amr_unmapcmd(struct amr_command *ac);
static intamr_start(struct amr_command *ac);
+ static intamr_start1(struct amr_softc *sc, struct amr_command *ac);
static void amr_complete(void *context, int pending);
+ static void amr_setup_dmamap(void *arg, bus_dma_segment_t *segs, int
nsegments, int error);
+ static void amr_setup_data_dmamap(void *arg, bus_dma_segment_t *segs, int
nsegments, int error);
/*
* Status monitoring
***
*** 150,155
--- 153,159
static intamr_quartz_submit_command(struct amr_softc *sc);
static intamr_quartz_get_work(struct amr_softc *sc, struct amr_mailbox
*mbsave);
static intamr_quartz_poll_command(struct amr_command *ac);
+ static intamr_quartz_poll_command1(struct amr_softc *sc, struct
amr_command *ac);
static intamr_std_submit_command(struct amr_softc *sc);
static intamr_std_get_work(struct amr_softc *sc, struct amr_mailbox
*mbsave);
***
*** 217,222
--- 221,227
sc-amr_submit_command = amr_quartz_submit_command;
sc-amr_get_work = amr_quartz_get_work;
sc-amr_poll_command = amr_quartz_poll_command;
+ sc-amr_poll_command1 = amr_quartz_poll_command1;
} else {
sc-amr_submit_command = amr_std_submit_command;
sc-amr_get_work = amr_std_get_work;
***
*** 681,690
if ((ac = amr_alloccmd(sc)) == NULL)
goto out;
/* allocate the response structure */
! if ((result = malloc(bufsize, M_DEVBUF, M_NOWAIT)) == NULL)
goto out;
/* set command flags */
! ac-ac_flags |= AMR_CMD_PRIORITY | AMR_CMD_DATAOUT;
/* point the command at our data */
ac-ac_data = result;
--- 686,696
if ((ac = amr_alloccmd(sc)) == NULL)
goto out;
/* allocate the response structure */
! if ((result = malloc(bufsize, M_DEVBUF, M_ZERO|M_NOWAIT)) == NULL)
goto out;
/* set command flags */
!
! ac-ac_flags |= AMR_CMD_PRIORITY | AMR_CMD_DATAIN;
Re: Can FreeBSD be installed on DellPowerEdge2800 ?
David Sze wrote: On Wed, Mar 02, 2005 at 08:25:40AM -0600, Art Mason wrote: Vinny Abello wrote: At 05:50 PM 3/1/2005, Art Mason wrote: Indeed, just installed on a customer's server last night, and I build SMP support into the GENERIC kernel this morning. Only issues I encountered has to do w/ recognizing the full 4GB of RAM, but this apparently has some compatibility issues w/ the amr driver. As per Holger's comments about disabling USB in BIOS, this is a good suggestion, since the DRAC apparently causes some IRQ issues w/ the PS/2 keyboard controller, or something along those lines. Regardless, these 2850 boxes are stupid fast, and I'm looking forward to benchmarking 5.3 on them. FYI, the architecture of the 2850 (assuming it is similar to your 2800) requires that you enable PAE support in your kernel of whatever OS you run to address the full 4GB of RAM. This is due in some part because of the memory mapping that was done for the PCI express bus and/or onboard Perc controller (per Dell tech support). We've run into this with all of our 2850's with various OS's and enabling PAE (per Dell's advice) fixes it. Yeah, I cam across that on some mailing list archives, but saw some additional references that this can cause issues with the amr driver. Have you experienced any instability issues with the amr driver and PAE enabled? If not, then I'll give this a shot on one of our lab boxes for testing. Thanks for the suggestion, BTW. On my 2850 the upper 1GB of RAM cannot be addressed without PAE support in the kernel. However, amr in 4.11-RELEASE does indeed seem to have trouble with PAE. The result being that with the option in the kernel, the root device (ufs:/dev/amrd0s1a) cannot be found. I backported scottl's amr PAE fixes from RELENG_5; the diffs applied cleanly (with offsets). I'm happy to report that my 2850 can now address its full 4GB and see its amr volumes. The diff against 4.11-RELEASE is attached, hopefully someone will be willing to commit it to RELENG_4. I don't have the cycles to watch after RELENG_4, so I'll have to take your word that this works. What date is this patch against? I committed some follow-up fixes last week that are required for management apps to work (and yes, LSI is getting ready to support FreeBSD with management apps). Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel trap 12 with interrupts disabled, 5.3-stable
I have updated a system from FreeBSD 4.10 to 5.3 (I did a fresh new installation from scatch). At the same time we put a new CPUs in there. The system is now a dual Xenon 3.2 GHZ with hyperthreading. When there's load on the server, it crashes. Here is what I get on the console: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 07 fault virtual address = 0x8 fault code = supervisor write, page not present instruction pointer = 0x8:0xc064973e stack pointer = 0x10:0xe338fc00 frame pointer = 0x10:0xe338fc0c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 1 (init) trap number = 12 panic: page fault cpuid = 3 spin lock sleepq chain held by 0xc22ad320 for 5 seconds What could be the cause? The system was very stable with FreeBSD 4.10 and only 2 CPUs (1 real and 1 virtual). When I've seen page faults in the past, it was caused by the RAM or the motherboard. Is it almost always the case? Does the fact to add 2 new CPUs is more likely to reveal a RAM problem that was not known before? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel trap 12 with interrupts disabled, 5.3-stable
Am Mittwoch, 9. März 2005 03:04 schrieb Pierre-Luc Drouin: I have updated a system from FreeBSD 4.10 to 5.3 (I did a fresh new installation from scatch). At the same time we put a new CPUs in there. [...] What could be the cause? The non-technical answer: FreeBSD 5.4 is in the release cycle with an upcoming 5.4 iso image. There were enormous efforts in improving FreeBSD 5.x, so if you already broke your system take the chance and get the new 5.4 system which probably fixes your problem. Next thing is that you won't see any benefit when enabling hyperthreading. It's strongly depending on the system's kind of load but almost everytime you'll see performance degradation. The system was very stable with FreeBSD 4.10 and only 2 CPUs (1 real and 1 virtual). When I've seen page faults in the past, it was caused by the RAM or the motherboard. Is it almost always the case? Does the fact to Maybe, but first you have to provide more information and make sure it frequently crashes at different points. Keep patience till anyone of the experts answers, in the meantime you can have a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html for providing more information. -Mano add 2 new CPUs is more likely to reveal a RAM problem that was not known before? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] pgpj8UOXRt76a.pgp Description: PGP signature
Re: Can FreeBSD be installed on DellPowerEdge2800 ?
At 05:55 PM 08/03/2005 -0700, Scott Long wrote this to All: David Sze wrote: On Wed, Mar 02, 2005 at 08:25:40AM -0600, Art Mason wrote: Yeah, I cam across that on some mailing list archives, but saw some additional references that this can cause issues with the amr driver. Have you experienced any instability issues with the amr driver and PAE enabled? If not, then I'll give this a shot on one of our lab boxes for testing. Thanks for the suggestion, BTW. On my 2850 the upper 1GB of RAM cannot be addressed without PAE support in the kernel. However, amr in 4.11-RELEASE does indeed seem to have trouble with PAE. The result being that with the option in the kernel, the root device (ufs:/dev/amrd0s1a) cannot be found. I backported scottl's amr PAE fixes from RELENG_5; the diffs applied cleanly (with offsets). I'm happy to report that my 2850 can now address its full 4GB and see its amr volumes. The diff against 4.11-RELEASE is attached, hopefully someone will be willing to commit it to RELENG_4. I don't have the cycles to watch after RELENG_4, so I'll have to take your word that this works. What date is this patch against? I committed some follow-up fixes last week that are required for management apps to work (and yes, LSI is getting ready to support FreeBSD with management apps). The patch is against 4.11-RELEASE, and is just a backport of your commit from Dec. 5th (http://lists.freebsd.org/pipermail/cvs-all/2004-December/094923.html). There haven't been any changes to amr since release, so it should apply directly to RELENG_4 as well. I left out the subsequent ioctl fixes and LSI 320-2E support. They look straightforward, but I don't have the software or hardware to test them. If you'd like them in there before committing to RELENG_4, I can take a stab at it and post a new patch. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: consistent problem with pcm0 audio
On 2005-03-08, Will Saxon scribbled these curious markings: I am using FreeBSD 5-STABLE from Feb 23rd with an onboard VIA VT8237/Avance Logic ALC200 sound controller. Periodically, sound will stop working. I will get the last note (sound packet?) repeated over and over until I close the program. Any further attempt to play a sound will cause the same note to be repeated. I am not able to reload the driver. Correct sound is restored when I reboot the computer. Couple of things that I've found will muck up your sound: o ACPI, as you mentioned. Be glad that you can even get your system to boot with ACPI. Mine crashes within 10 seconds of hitting Enter at the boot menu. o Threading libraries. games/doomlegacy exhibits behaviour endemic of a sound buffering / channel issue (sound stuttering and playing slowly during periods of high activity, working better during periods of less activity) for me when it runs with libpthread. I spent *hours* (okay, I'm a Doom addict, I'll admit it) trying to diagnose the problem in the mindset that it was a buffering / channel problem, when all I had to do was set it to use libc_r in libmap.conf. Best Regards, Christopher Nehren -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson If you ask the wrong questions, you get answers like 42 and God. Unix is user friendly. However, it isn't idiot friendly. ___ 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-PRERELEASE cPanel
Hello, I was wondering after upgrading a box today it broke my cPanel setup since it rsync out of their master servers to paths like FreeBSD-x.x-RELEASE or -STABLE , so is it possible to switch back to freebsd 5.3-STABLE or change the uname output for their scripts to work? Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Mozilla Firefox problem
Each time i start Mozilla Firefox it starts from scratch and asks if i want to import my previous bookmarks etc .. why is this occurying and how do i fix it ? -- Yours Sincerely Shinjii http://www.shinji.nq.nu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ad0 errors on FBSD 4.11-RELEASE
Since moving my machine, I've been having all kinds of issues with ad0. Here's one example: Mar 9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: timeout waiting for READY Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ad0: timeout sending command=00 s=d0 e=04 Mar 9 06:26:23 flake /kernel: ad0: flush queue failed Mar 9 06:26:23 flake /kernel: - resetting Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: WRITE command timeout tag=1 serv=0 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ad0: timeout waiting for READY Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: - resetting Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done These issues have been resulting in spontaneous reboots; presumably from kernel panics. Any ideas what could be causing this? I'm running vinum, if that matters. I guess if I need to I can run both drives off the second IDE controller... is there any magic I'd need to do in vinum to accomplish that? -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming, or what? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
