Re: MCA messages after upgrade to 8.2-BEAT1
On Wed, Dec 22, 2010 at 09:57:26AM -0500 I heard the voice of John Baldwin, and lo! it spake thus: > > You are getting corrected ECC errors in your RAM. Actually, don't > CPU 0 0 data cache > ADDR 236493c0 > Data cache ECC error (syndrome 1c) > CPU 0 1 instruction cache > ADDR 2a1c9440 > Instruction cache ECC error > CPU 0 2 bus unit > L2 cache ECC error > CPU 1 0 data cache > ADDR 23649640 > Data cache ECC error (syndrome 1c) > CPU 1 1 instruction cache > ADDR 2a1c9440 > Instruction cache ECC error > CPU 1 2 bus unit > L2 cache ECC error suggest CPU cache, not RAM? (that's actually a question; I don't know, but that's what a naive reading suggests...) -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
happy hacker lite 2 keyboard
Dear all! I consider buying new keyboard and found happy hacker lite 2 model suiting fine. Is there someone on the list with expe- rience using it? I'm aware I should change rc.conf to meet it's 65 key layout. Also, how xorg.conf has to look like in this situation? Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Sense fetching [Was: cdrtools /devel ...]
On Sun, Nov 14, 2010 at 9:32 AM, Alexander Motin wrote: > Brandon Gooch wrote: >> On Sat, Nov 13, 2010 at 3:34 AM, Alexander Motin wrote: >>> Now uncommitted pass_autosence.patch and possibly cdrtools.patch. >> >> OK. Patched kernel and cdrtools has resulted in a working cdrecord >> (burned an ISO successfully) and an endless stream of: >> >> ... >> (pass0:ata0:0:0:0): Requesting SCSI sense data >> (pass0:ata0:0:0:0): SCSI status error >> (pass0:ata0:0:0:0): Requesting SCSI sense data >> (pass0:ata0:0:0:0): SCSI status error >> (pass0:ata0:0:0:0): Requesting SCSI sense data >> (pass0:ata0:0:0:0): SCSI status error >> (pass0:ata0:0:0:0): Requesting SCSI sense data >> (pass0:ata0:0:0:0): SCSI status error >> ... > > I think it can be hald probing for media insertion. Probably we should > slightly reduce error logging verbosity. May be somehow make to not log > errors on requests submitted from user-level via pass driver. > >> But most important part: It works, and it burned very quickly! The CD >> was created, and fully functional (I booted the Fedora image and >> completed an installation). > > Nice! What are your thoughts on committing this (or something like it)? Should I just keep a local patch set for the semi-long-term? Do you have something else in the works? -Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
Zoran wrote: I consider buying new keyboard and found happy hacker lite 2 model suiting fine. Is there someone on the list with expe- rience using it? I have one in use since ~5 years. The typing feel is a lot better compared to the Logitech keyboard I had before. The only problem I have with mine is that it's not usable with the boot loader menu. It seems to be hardware related as it works fine with other computers (using different chipsets). I'm aware I should change rc.conf to meet it's 65 key layout. Also, how xorg.conf has to look like in this situation? The only keyboard-specific thing I have in my rc.conf is 'keymap="us.iso"'. My xorg.conf contains the following entries in the "InputDevice" section: Option "XkbRules" "xorg" Option "XkbModel" "pc101" Option "XkbLayout" "us" I say it should work right out of the box ;-) In addition, I did configure a .xmodmaprc to get umlauts, etc. HTH, Philipp
Re: MCA messages after upgrade to 8.2-BEAT1
2010/12/23 Dan Langille > On 12/22/2010 9:57 AM, John Baldwin wrote: > >> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: >> >>> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 >>> Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, >>> Status 0x >>> Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, >>> APIC ID 0 >>> Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD >>> Memory >>> Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 >>> >> >> You are getting corrected ECC errors in your RAM. You see them once an >> hour >> because we poll the machine check registers once an hour. If this happens >> constantly you might have a DIMM that is dying? >> > > John: > > I take it these ECC errors *may* have been happening for some time. What > has changed is the OS now polls for the errors and reports them. > > Yes, we enabled MCA by default in 8.1-RELEASE. Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Sense fetching [Was: cdrtools /devel ...]
Brandon Gooch wrote: > On Sun, Nov 14, 2010 at 9:32 AM, Alexander Motin wrote: >> Brandon Gooch wrote: >>> On Sat, Nov 13, 2010 at 3:34 AM, Alexander Motin wrote: Now uncommitted pass_autosence.patch and possibly cdrtools.patch. >>> OK. Patched kernel and cdrtools has resulted in a working cdrecord >>> (burned an ISO successfully) and an endless stream of: >>> >>> ... >>> (pass0:ata0:0:0:0): Requesting SCSI sense data >>> (pass0:ata0:0:0:0): SCSI status error >>> (pass0:ata0:0:0:0): Requesting SCSI sense data >>> (pass0:ata0:0:0:0): SCSI status error >>> (pass0:ata0:0:0:0): Requesting SCSI sense data >>> (pass0:ata0:0:0:0): SCSI status error >>> (pass0:ata0:0:0:0): Requesting SCSI sense data >>> (pass0:ata0:0:0:0): SCSI status error >>> ... >> I think it can be hald probing for media insertion. Probably we should >> slightly reduce error logging verbosity. May be somehow make to not log >> errors on requests submitted from user-level via pass driver. >> >>> But most important part: It works, and it burned very quickly! The CD >>> was created, and fully functional (I booted the Fedora image and >>> completed an installation). >> Nice! > > What are your thoughts on committing this (or something like it)? > Should I just keep a local patch set for the semi-long-term? Do you > have something else in the works? I wanted to do something with these logs first, as they are hardly acceptable, but was distracted by different project. Unless somebody take it, I'll be back to it later. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
On 25/12/2010, at 5:15, Philipp Ost wrote: > The only problem I have with mine is that it's not usable with the boot > loader menu. It seems to be hardware related as it works fine with other > computers (using different chipsets). If it's a USB keyboard then it's up to your BIOS if it will work in the loader. ie it needs to probe for USB devices and be able to parse the keyboard messages on behalf of the loader. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Re: MCA messages after upgrade to 8.2-BEAT1
Alan Cox writes: > 2010/12/23 Dan Langille > >> On 12/22/2010 9:57 AM, John Baldwin wrote: >> >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: >>> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, Status 0x Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, APIC ID 0 Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD Memory Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 >>> >>> You are getting corrected ECC errors in your RAM. You see them once an >>> hour >>> because we poll the machine check registers once an hour. If this happens >>> constantly you might have a DIMM that is dying? >>> >> >> John: >> >> I take it these ECC errors *may* have been happening for some time. What >> has changed is the OS now polls for the errors and reports them. >> >> > Yes, we enabled MCA by default in 8.1-RELEASE. Is there some reason that it is only available for i386 and not for amd64? Linux has something called mcelog, for machine check errors, which sounds similar and is available for amd64. -- Carl Johnsonca...@peak.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MCA messages after upgrade to 8.2-BEAT1
On Fri, Dec 24, 2010 at 5:08 PM, Carl Johnson wrote: > Alan Cox writes: > > > 2010/12/23 Dan Langille > > > >> On 12/22/2010 9:57 AM, John Baldwin wrote: > >> > >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: > >>> > Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 > Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, > Status 0x > Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, > APIC ID 0 > Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD > Memory > Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 > > >>> > >>> You are getting corrected ECC errors in your RAM. You see them once an > >>> hour > >>> because we poll the machine check registers once an hour. If this > happens > >>> constantly you might have a DIMM that is dying? > >>> > >> > >> John: > >> > >> I take it these ECC errors *may* have been happening for some time. What > >> has changed is the OS now polls for the errors and reports them. > >> > >> > > Yes, we enabled MCA by default in 8.1-RELEASE. > > Is there some reason that it is only available for i386 and not for > amd64? Linux has something called mcelog, for machine check errors, > which sounds similar and is available for amd64. > > Perhaps I'm misunderstanding your question, but our MCA driver is supported and enabled by default on both i386 and amd64. Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MCA messages after upgrade to 8.2-BEAT1
On Fri, Dec 24, 2010 at 03:08:48PM -0800, Carl Johnson wrote: > Alan Cox writes: > > > 2010/12/23 Dan Langille > > > >> On 12/22/2010 9:57 AM, John Baldwin wrote: > >> > >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: > >>> > Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 > Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, > Status 0x > Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, > APIC ID 0 > Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD > Memory > Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 > > >>> > >>> You are getting corrected ECC errors in your RAM. You see them once an > >>> hour > >>> because we poll the machine check registers once an hour. If this happens > >>> constantly you might have a DIMM that is dying? > >>> > >> > >> John: > >> > >> I take it these ECC errors *may* have been happening for some time. What > >> has changed is the OS now polls for the errors and reports them. > >> > >> > > Yes, we enabled MCA by default in 8.1-RELEASE. > > Is there some reason that it is only available for i386 and not for > amd64? Linux has something called mcelog, for machine check errors, > which sounds similar and is available for amd64. You mean like what John used in his earlier post on this thread? :-) http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060705.html If you're looking for it for FreeBSD, it's available below as a patch to the original (I believe): http://www.FreeBSD.org/~jhb/mcelog/ -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MCA messages after upgrade to 8.2-BEAT1
Alan Cox writes: > On Fri, Dec 24, 2010 at 5:08 PM, Carl Johnson wrote: > >> Alan Cox writes: >> >> > 2010/12/23 Dan Langille >> > >> >> On 12/22/2010 9:57 AM, John Baldwin wrote: >> >> >> >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: >> >>> >> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 >> Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, >> Status 0x >> Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, >> APIC ID 0 >> Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD >> Memory >> Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 >> >> >>> >> >>> You are getting corrected ECC errors in your RAM. You see them once an >> >>> hour >> >>> because we poll the machine check registers once an hour. If this >> happens >> >>> constantly you might have a DIMM that is dying? >> >>> >> >> >> >> John: >> >> >> >> I take it these ECC errors *may* have been happening for some time. What >> >> has changed is the OS now polls for the errors and reports them. >> >> >> >> >> > Yes, we enabled MCA by default in 8.1-RELEASE. >> >> Is there some reason that it is only available for i386 and not for >> amd64? Linux has something called mcelog, for machine check errors, >> which sounds similar and is available for amd64. >> >> > Perhaps I'm misunderstanding your question, but our MCA driver is supported > and enabled by default on both i386 and amd64. Thanks, it appears that I misunderstood. I ran whereis and found /usr/src/sbin/mca and didn't find it on my amd64 system. I do see it in my sysctl listing now that I look there. -- Carl Johnsonca...@peak.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MCA messages after upgrade to 8.2-BEAT1
Jeremy Chadwick writes: > On Fri, Dec 24, 2010 at 03:08:48PM -0800, Carl Johnson wrote: >> Alan Cox writes: >> >> > 2010/12/23 Dan Langille >> > >> >> On 12/22/2010 9:57 AM, John Baldwin wrote: >> >> >> >>> On Wednesday, December 22, 2010 7:41:25 am Miroslav Lachman wrote: >> >>> >> Dec 21 12:42:26 kavkaz kernel: MCA: Bank 0, Status 0xd40e4833 >> Dec 21 12:42:26 kavkaz kernel: MCA: Global Cap 0x0105, >> Status 0x >> Dec 21 12:42:26 kavkaz kernel: MCA: Vendor "AuthenticAMD", ID 0x40f33, >> APIC ID 0 >> Dec 21 12:42:26 kavkaz kernel: MCA: CPU 0 COR OVER BUSLG Source DRD >> Memory >> Dec 21 12:42:26 kavkaz kernel: MCA: Address 0x236493c0 >> >> >>> >> >>> You are getting corrected ECC errors in your RAM. You see them once an >> >>> hour >> >>> because we poll the machine check registers once an hour. If this >> >>> happens >> >>> constantly you might have a DIMM that is dying? >> >>> >> >> >> >> John: >> >> >> >> I take it these ECC errors *may* have been happening for some time. What >> >> has changed is the OS now polls for the errors and reports them. >> >> >> >> >> > Yes, we enabled MCA by default in 8.1-RELEASE. >> >> Is there some reason that it is only available for i386 and not for >> amd64? Linux has something called mcelog, for machine check errors, >> which sounds similar and is available for amd64. > > You mean like what John used in his earlier post on this thread? :-) > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060705.html Oops! Yes, I missed that when I read it. > If you're looking for it for FreeBSD, it's available below as a patch to > the original (I believe): > > http://www.FreeBSD.org/~jhb/mcelog/ Thanks for the link. -- Carl Johnsonca...@peak.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
Thaks for reply. > I have one in use since ~5 years. The typing feel is a lot better compared > to the Logitech keyboard I had before. > The only problem I have with mine is that it's not usable with the boot > loader menu. It seems to be hardware related as it works fine with other > computers (using different chipsets). There is always chance to use it with ps2 converter. All new keyboards are usb in fact, but I add that little plastic in between. > The only keyboard-specific thing I have in my rc.conf is 'keymap="us.iso"'. K. Then I have to change nothing. > My xorg.conf contains the following entries in the "InputDevice" section: > Option "XkbRules" "xorg" > Option "XkbModel" "pc101" > Option "XkbLayout" "us" I don't have this. Should be easy to check out if necessary. > I say it should work right out of the box ;-) In addition, I did configure > a .xmodmaprc to get umlauts, etc. Yep, I assume I would have to change my xmodmaprc to match new layout. The other part is that fvwm2rc uses that layout to have extra tweaks for window manager. I still have something to ponder. To have more than one screen in fvwm, actually four of them, I ought to turn off numpad first. Then I use com- bination of Alt-Fx to jump here and there. In bios I removed numpad and it is not working on the kb, to my wish. Any thought how it goes on HH? Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
