Re: Odd IDE / vinum problem on new 4.9-RC3 system
Serious Signal wrote: Well colleagues, but both of you failed to specify your onboard IDE controlled dmesg lines! ;-) *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** Dmitry, Good catch! atapci0: VIA 82C686 ATA100 controller port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 In my case, the motherboard came in a Shuttle XPC (Flex ATX form factor) barebones model FV24 which uses the VIA VT82C686B chipset. It has the latest available BIOS installed. And my case again: atapci0: VIA 82C596 ATA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [...] ata1-slave: ATA identify retries exceeded ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA66 acd0: CDROM GCR-8521B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad0s1a: UDMA ICRC error reading fsbn 181887 of 90912-91039 (ad0s1 bn 181887; cn 11 tn 82 sn 6) retrying ad0s1a: UDMA ICRC error reading fsbn 181887 of 90912-91039 (ad0s1 bn 181887; cn 11 tn 82 sn 6) retrying ad0s1a: UDMA ICRC error reading fsbn 181887 of 90912-91039 (ad0s1 bn 181887; cn 11 tn 82 sn 6) retrying ad0s1a: UDMA ICRC error reading fsbn 181887 of 90912-91039 (ad0s1 bn 181887; cn 11 tn 82 sn 6) falling back to PIO mode Motherboard is most probably ASUS, P2B or of that family. Regards, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-PRE - if_xe.ko failed to register
Date: Wed, 01 Oct 2003 09:25:09 -0400 From: Zeno Sirbu [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi, Maybe this message should go to mobile. Machine: IBM ThinkPad 600 (Model 2645-85U) PII-300, 64 RAM, 4GB HDD Network card: Xircom CE3B-100BTX (pcmcia) I've SUP yesterday (Sept 30) from cvsup12.freebsd.org , make world, mergemaster, MAKEDEV, updated /stand , rebooted, everyting seems to be ok but I'm getting an error related to the pcmcia network card. uname -a : FreeBSD thinkpad600.sprintnet.ca 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Tue Sep 30 23:25:10 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 (from dmesg) : pccard: card inserted, slot 0 xe0 at port 0x240-0x24f iomem 0xd1000-0xd1fff irq 3 slot 0 on pccard0 xe0: Xircom CE3, bonding version 0x45, 100Mbps capable xe0: DingoID = 0, RevisionID = 0, VendorID = 0 xe0: Ethernet address 00:80:c7:ea:2c:c6 xe0: watchdog timeout; resetting card After reset the card starts to function normally (gets an IP from DHCP server, etc.). Can somebody help? What I'm doing wrong ? This is absolutely normal. (Not ideal, but normal.) The two messages about the module load failure simply indicate that the xe driver is already present...eith built into the kernel or already loaded when the card is probed. Ideally the pccardd should check whether the driver is already present and not try to load it, but it's not quite that simple as the driver module may be loaded at boot time (via loader.conf) or built into the kernel. The watchdog timeout is also normal. The author of the xe driver recently patched the driver in CURRENT to try to eliminate this initialization problem, but I have not tried my card recently, so I don't know if the issue is fully resolved. In any case, the only effect of this is a 5 second delay when the card starts. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Expert input required: P4 odd signals, no apparent memory fault, DISABLE_PSE?
I'm tracking -STABLE on a 1.8GHz P4 with 512MB of memory. Roughly since the PAE changes were MFCed, I've been seeing memory-corruption-related errors under specific circumstances: for example, a run of portsdb -fUu can be guaranteed to generate SIGBUS, SIGILL and SIGSEGVs in a handful of sh, sed, etc. processes. However, reverting to a 4.8 kernel from prior to September either hides/masks these errors, or no longer triggers them. The memory/mobo _appears_ to check out OK under (ferinstance) extended runs of memtest86. Now, on -current I've seen reference to the DISABLE_PSE kernel option, and some discussion that this behaviour may be due to a processor/timing bug. So I have the following questions which I'd appreciate an expert giving a definitive opinion on (I'm no x86/hardware hacker, me): - are these problems potentially caused by this bug? - what exactly does DISABLE_PSE do? (it's undocumented and a one-para explanation of the expected behaviour of this option would be appreciated) - were any commits around the time of the MFC of the PAE code liable to have introduced problems into the kernel which this workaround might address? I know it's a lot to ask, but both hardware and OS have been rock-solid up until this point. Although I've not conclusively ruled out hardware faults, the continued stability under high load of a pre-september 4.8 kernel makes me suspicious that this is more likely to be a bug getting tickled than I'd normally suspect from these symptoms. I'm about to experiment with this option but it currently feels a little like cargo-cult admin. If there are any definitive tests that would indicate if this hardware problem is present and addressed by this, that's be nice to know too. Cheers, jan -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ No generalised law is without exception. A self-demonstrating axiom. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expert input required: P4 odd signals, no apparent memory fault, DISABLE_PSE?
How recent is your copy of RELENG_4 ? The PSE disable code was committed to the tree already as well as a fix so it would work with APM on the 17th. By default it is disabled. If you look at your dmesg.boot you should see Warning: Pentium 4 CPU: PSE disabled ---Mike At 11:38 AM 20/10/2003, Jan Grant wrote: I'm tracking -STABLE on a 1.8GHz P4 with 512MB of memory. Roughly since the PAE changes were MFCed, I've been seeing memory-corruption-related errors under specific circumstances: for example, a run of portsdb -fUu can be guaranteed to generate SIGBUS, SIGILL and SIGSEGVs in a handful of sh, sed, etc. processes. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expert input required: P4 odd signals, no apparent memoryfault, DISABLE_PSE?
On Mon, 20 Oct 2003, Mike Tancsa wrote: How recent is your copy of RELENG_4 ? The PSE disable code was committed to the tree already as well as a fix so it would work with APM on the 17th. By default it is disabled. If you look at your dmesg.boot you should see Warning: Pentium 4 CPU: PSE disabled Latest was pre-weekend; I'm just completing a fresh build now, so I hope this'll lick the problem, thanks. (Incidentally this might well be worth documenting in UPDATING since it's an issue that's been plaguing me [and a few correspondents, according to emails I've had] for a while.) -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Prolog in JavaScript: http://ioctl.org/logic/prolog-latest ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SIS 651 chip set, ata problem
Hi! We're trying to install FreeBSD 4.9/RC on a system with a Asus P4S533-MX board (SIS 651 chipset). This does not work with UDMA enabled. Is this problem known? Is there a work-around? Greetings, Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Solved. Re: Expert input required: P4 odd signals, no apparent memoryfault, DISABLE_PSE?
On Mon, 20 Oct 2003, Jan Grant wrote: On Mon, 20 Oct 2003, Mike Tancsa wrote: How recent is your copy of RELENG_4 ? The PSE disable code was committed to the tree already as well as a fix so it would work with APM on the 17th. By default it is disabled. If you look at your dmesg.boot you should see Warning: Pentium 4 CPU: PSE disabled Latest was pre-weekend; I'm just completing a fresh build now, so I hope this'll lick the problem, thanks. (Incidentally this might well be worth documenting in UPDATING since it's an issue that's been plaguing me [and a few correspondents, according to emails I've had] for a while.) Well, I'm pleased to report what looks like success: as Mike indicated, PSE is now disabled automatically by default. I've tried repeating the activities which have recently been triggering memory corruption - so far with no ill effects. I'll keep the stress tests running overnight. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ I think therefore I am. -- Ronnie Descartes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SIS 651 chip set, ata problem
On Mon, 20 Oct 2003 20:29:50 +0200 (CEST) Peter Spekreijse [EMAIL PROTECTED] wrote: Hi! We're trying to install FreeBSD 4.9/RC on a system with a Asus P4S533-MX board (SIS 651 chipset). This does not work with UDMA enabled. Is this problem known? Is there a work-around? Yes, this problem is known (PR-43345). Unfortunately, it is not very easily fixed under 4-stable (I believe -current already has a fix for this) according to the people who are experts on the ATA code. Workaround, here is my experience: http://geekinfo.net/article.php?story=20021229152603904 Basically, if your BIOS allows you to turn off ultra-dma, you will get FreeBSD installed. The patch described in PR-43345 works for me, but YMMV, because I use a 20G ATA66 hard drive. Hope this helps a bit. -- Torfinn Ingolfsen, Norway ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
hpt374 + freebsd 4.8 (epox mainboard)
i have that on boot:
ata0: reseting device ...done
acd0: MODE_SENSE_BIG command timeout - reseting
and next time , next time , and next time .. :
hardware/software configuration:
freebsd 4.8
epox mainboard 4pca3+ (intel 875p)
hpt374
two maxtor hard disks (raid 1)
when i turn off hpt374 (in bios), the situation is the same.
any help ideas?
regards.
--
__ ___ ___ _
[Lukasz Kowalczyk][neos(at)of.pl] / _ \| __| _ \ |
[main(){while(1){fork();}}] | (_) | _|| _/ |__
[Security Officer/Administrator] \___/|_(_)_| ||
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
kern/53717: 4.8-RELEASE kernel panic (page fault)
Anyone knows howt to solve this prob? Keith. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
