DMESG question
I have two small questions: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: # dmesg arp info overwritten for 193.231.39.129 by 00:90:bf:10:88:40 on vr0 arp info overwritten for 193.231.39.129 by 00:10:dc:4c:6f:6c on vr0 arp info overwritten for 193.231.39.36 by 00:15:f2:16:f8:b4 on vr0 arp info overwritten for 193.231.39.54 by 00:e0:29:9b:bc:6c on vr0 ... (and a lot of other similar messages, similar if not even identical) Most questions on this mail list require me to provide a valid output of dmesg. But if old messages are erased, how am I supposed to do this? I am not allowed to reboot the machine! The machine is supposed to be running 24/7, NO reboot allowed. 2) What do these lines mean (the lines I copied above from the output of `dmesg`)? NOTE: I'm using OpenBSD 3.8 on i386 (P4). Yours in BSDness, Gabriel George POPA
Re: DMESG question
Gabriel, You can always pipe it to more, like this # dmesg | more and you can make the output go to a file, with # dmesg filename Regards, Loz On 8/7/06, Gabriel George POPA [EMAIL PROTECTED] wrote: I have two small questions: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: # dmesg arp info overwritten for 193.231.39.129 by 00:90:bf:10:88:40 on vr0 arp info overwritten for 193.231.39.129 by 00:10:dc:4c:6f:6c on vr0 arp info overwritten for 193.231.39.36 by 00:15:f2:16:f8:b4 on vr0 arp info overwritten for 193.231.39.54 by 00:e0:29:9b:bc:6c on vr0 ... (and a lot of other similar messages, similar if not even identical) Most questions on this mail list require me to provide a valid output of dmesg. But if old messages are erased, how am I supposed to do this? I am not allowed to reboot the machine! The machine is supposed to be running 24/7, NO reboot allowed. 2) What do these lines mean (the lines I copied above from the output of `dmesg`)? NOTE: I'm using OpenBSD 3.8 on i386 (P4). Yours in BSDness, Gabriel George POPA
Re: DMESG question
Hi Gabriel, old versions of /var/log/messages are stored in a gzip compressed form in /var/log too and are called messages.number.gz steffen -- http://cdp.doomed-reality.org why the 'never ending story' makes the 'mission impossible' in /bin/sh: while [ 1 ]; do sleep 1; done; do_mission;
Re: DMESG question
On 2006/08/07 16:15, Gabriel George POPA wrote: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: /var/log/messages if they're not rotated too far away (change newsyslog.conf if you want to keep them for longer). # dmesg arp info overwritten for 193.231.39.129 by 00:90:bf:10:88:40 on vr0 arp info overwritten for 193.231.39.129 by 00:10:dc:4c:6f:6c on vr0 arp info overwritten for 193.231.39.36 by 00:15:f2:16:f8:b4 on vr0 arp info overwritten for 193.231.39.54 by 00:e0:29:9b:bc:6c on vr0 this is IP addresses moving between machines.
Re: DMESG question
On 8/7/06, Gabriel George POPA [EMAIL PROTECTED] wrote: I have two small questions: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? There is always a copy of the original dmesg in /var/run/dmesg.boot Landry
Re: DMESG question
All right, even better. Thank you all. Yours in BSDness, George Landry wrote: On 8/7/06, Gabriel George POPA [EMAIL PROTECTED] wrote: I have two small questions: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? There is always a copy of the original dmesg in /var/run/dmesg.boot Landry
Re: DMESG question
Thank you, that's what I was looking for :) Stuart Henderson wrote: On 2006/08/07 16:15, Gabriel George POPA wrote: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: /var/log/messages if they're not rotated too far away (change newsyslog.conf if you want to keep them for longer). # dmesg arp info overwritten for 193.231.39.129 by 00:90:bf:10:88:40 on vr0 arp info overwritten for 193.231.39.129 by 00:10:dc:4c:6f:6c on vr0 arp info overwritten for 193.231.39.36 by 00:15:f2:16:f8:b4 on vr0 arp info overwritten for 193.231.39.54 by 00:e0:29:9b:bc:6c on vr0 this is IP addresses moving between machines.
Re: DMESG question
On Monday 07 August 2006 08:15, Gabriel George POPA wrote: Most questions on this mail list require me to provide a valid output of dmesg. But if old messages are erased, how am I supposed to do this? Take a look at /var/run/dmesg.boot. Dan RamaleyDial Center 118, Drake University Network Programmer/Analyst 2407 Carpenter Ave +1 515 271-4540Des Moines IA 50311 USA
Re: DMESG question
Cituji Gabriel George POPA [EMAIL PROTECTED]: I have two small questions: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: # dmesg arp info overwritten for 193.231.39.129 by 00:90:bf:10:88:40 on vr0 arp info overwritten for 193.231.39.129 by 00:10:dc:4c:6f:6c on vr0 arp info overwritten for 193.231.39.36 by 00:15:f2:16:f8:b4 on vr0 arp info overwritten for 193.231.39.54 by 00:e0:29:9b:bc:6c on vr0 ... (and a lot of other similar messages, similar if not even identical) man arp(4) - http://www.openbsd.org/cgi-bin/man.cgi?query=arpapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html#end jirib
Re: DMESG question
Stuart Henderson wrote: On 2006/08/07 16:15, Gabriel George POPA wrote: 1) When the OS generates too much messages, old messages are lost (oldest lines present in `dmesg` are lost). What can I do to see ALL messages ever recorded for dmesg printing? More precisely, take a look at my `dmesg`: /var/log/messages if they're not rotated too far away (change newsyslog.conf if you want to keep them for longer). PLEASE, NO. Bad advice. Either use the dmesg command or the /var/run/dmesg.boot DO NOT pull your dmesg out of messages if you are seriously expecting help from others. If for some reason messages is your only option, carefully edit out the date and time stuff before posting. If you just paste in your messages output raw, I'm unlikely to spend much time looking at your query. Some people may...but not me. Which would you rather dig through looking for the one little gem that explains a problem? This: Jul 24 09:03:27 njh-9 /bsd: OpenBSD 3.9-current (GENERIC) #922: Wed Jun 28 23:06 :50 MDT 2006 Jul 24 09:03:27 njh-9 /bsd: [EMAIL PROTECTED]:/usr/src/sys/arch/i386/ compile/GENERIC Jul 24 09:03:27 njh-9 /bsd: cpu0: Intel(R) Pentium(R) 4 CPU 1300MHz (GenuineInt el 686-class) 1.30 GHz Jul 24 09:03:27 njh-9 /bsd: cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PG E,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM Jul 24 09:03:27 njh-9 /bsd: real mem = 133296128 (130172K) Jul 24 09:03:27 njh-9 /bsd: avail mem = 114892800 (112200K) Jul 24 09:03:27 njh-9 /bsd: using 1652 buffers containing 6766592 bytes (6608K) of memory Jul 24 09:03:27 njh-9 /bsd: mainbus0 (root) Jul 24 09:03:27 njh-9 /bsd: bios0 at mainbus0: AT/286+(00) BIOS, date 11/30/00, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (97 entries) Jul 24 09:03:27 njh-9 /bsd: bios0: Dell Computer Corporation Dimension 8100 ... or this: OpenBSD 3.9-current (GENERIC) #922: Wed Jun 28 23:06:50 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 1300MHz (GenuineIntel 686-class) 1.30 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH, DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 133296128 (130172K) avail mem = 114892800 (112200K) using 1652 buffers containing 6766592 bytes (6608K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 11/30/00, BIOS32 rev. 0 @ 0xffe90, SMB IOS rev. 2.3 @ 0xf0450 (97 entries) bios0: Dell Computer Corporation Dimension 8100 ,,, All the date and time crap doesn't add anything for us, it just makes it completely unreadable, at least to me. If you want our help on something, MAKE IT EASY FOR US. Note how ugly that all looks, I was (intentionally) completely careless with the line wraps, and it STILL looks a lot better than some of the crap you guys post to the lists. But watch this: If I use my mail client smartly: OpenBSD 3.9-current (GENERIC) #922: Wed Jun 28 23:06:50 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 1300MHz (GenuineIntel 686-class) 1.30 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 133296128 (130172K) avail mem = 114892800 (112200K) using 1652 buffers containing 6766592 bytes (6608K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 11/30/00, BIOS32 rev. 0 @ 0xffe90, SMB IOS rev. 2.3 @ 0xf0450 (97 entries) bios0: Dell Computer Corporation Dimension 8100 ... wow...so much more readable (assuming I didn't really snip my dmesg, of course). Yes, it took at least ten seconds longer to do that than it did to stupidly copy/paste, but I can assure you, I'd spend a lot more time reading it without stupid wrapping. Nick.
Intel 82801 SMBus dmesg question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Had originally posted a message Tuning NFS File Transfer Speed and had eventually posted a Solved reply to it on the list. That turned out to be erroneous. It did turn out to be a hardware issue. Had some leaking capacitors on the old VIA Abit mobo and replaced it with a Aopen MX3ST mobo picked up on the cheap. All seems to be working okay so far, but my question concerns what dmesg is saying. I googled all over, searched in the archives, and came up with lots of dmesg's that mentioned it, but didn't explain specifically what that one line meant. It says: Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured Before asking anything on the list, I tried different things in the BIOS like disabling USB, the onboard NIC, juggled some IRQ's, just generally doing some experimenting, but the message is still there. I'd just like to know what exactly it means maybe be pointed to a site that explains it so I can learn more about it. Will put in output of dmesg ifconfig below. Thanks for all replies. Denny White - --- OpenBSD 3.8-stable (GENERIC) #4: Tue Jan 17 02:45:42 UTC 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 801 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 266969088 (260712K) avail mem = 236720128 (231172K) using 3284 buffers containing 13451264 bytes (13136K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(f4) BIOS, date 07/19/02, BIOS32 rev. 0 @ 0xfb140 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdef0/128 (6 entries) pcibios0: PCI Exclusive IRQs: 9 10 11 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xc000 0xcc000/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82815 Hub rev 0x04 vga1 at pci0 dev 2 function 0 Intel 82815 Graphics rev 0x04: aperture at 0xe000, size 0x400 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb0 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x05 pci1 at ppb0 bus 1 fxp0 at pci1 dev 8 function 0 Intel 82562 rev 0x03: irq 11, address 00:01:80:0b:76:77 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 xl0 at pci1 dev 10 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 11, address 00:01:03:1a:2f:21 bmtphy0 at xl0 phy 24: Broadcom 3C905C internal PHY, rev. 7 ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05 pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x05: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: WDC WD400BB-00AUA1 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd1 at pciide0 channel 0 drive 1: WDC WD300BB-00AUA1 wd1: 16-sector PIO, LBA, 28629MB, 58633344 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 4 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HP, CD-Writer+ 9500b, 1.06 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 uhci0 at pci0 dev 31 function 2 Intel 82801BA USB rev 0x05: irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured uhci1 at pci0 dev 31 function 4 Intel 82801BA USB rev 0x05: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered auich0 at pci0 dev 31 function 5 Intel 82801BA AC97 rev 0x05: irq 9, ICH2 AC97 ac97: codec id 0x41445360 (Analog Devices AD1885) ac97: codec features headphone, Analog Devices Phat Stereo audio0 at auich0 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 lm0 at isa0 port 0x290/8: W83627HF npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ed65 netmask ed65 ttymask fde7 pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches
Re: Intel 82801 SMBus dmesg question
On Fri, 27 Jan 2006, Denny White wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Had originally posted a message Tuning NFS File Transfer Speed and had eventually posted a Solved reply to it on the list. That turned out to be erroneous. It did turn out to be a hardware issue. Had some leaking capacitors on the old VIA Abit mobo and replaced it with a Aopen MX3ST mobo picked up on the cheap. All seems to be working okay so far, but my question concerns what dmesg is saying. I googled all over, searched in the archives, and came up with lots of dmesg's that mentioned it, but didn't explain specifically what that one line meant. It says: Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured Before asking anything on the list, I tried different things in the BIOS like disabling USB, the onboard NIC, juggled some IRQ's, just generally doing some experimenting, but the message is still there. I'd just like to know what exactly it means maybe be pointed to a site that explains it so I can learn more about it. Will put in output of dmesg ifconfig below. Thanks for all replies. There's nothing wrong. It just mean SMBus is not supported. SMBus is a system management bus. It is generally used to read and control fans, temperature sensors and such. It is not supported on 3.8, but 3.9 will support a wide variety of SMBus controllers. Install 3.9-beta to take a look. It's available on the various mirrors. The ichiic(4) and iic(4) man pages contain some more info. You can read them via the web site: http://www.openbsd.org/cgi-bin/man.cgi?query=ichiic -Otto
Re: Intel 82801 SMBus dmesg question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today Otto Moerbeek contributed the following: On Fri, 27 Jan 2006, Denny White wrote: Had originally posted a message Tuning NFS File Transfer Speed and had eventually posted a Solved reply to it on the list. That turned out to be erroneous. It did turn out to be a hardware issue. Had some leaking capacitors on the old VIA Abit mobo and replaced it with a Aopen MX3ST mobo picked up on the cheap. All seems to be working okay so far, but my question concerns what dmesg is saying. I googled all over, searched in the archives, and came up with lots of dmesg's that mentioned it, but didn't explain specifically what that one line meant. It says: Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured Before asking anything on the list, I tried different things in the BIOS like disabling USB, the onboard NIC, juggled some IRQ's, just generally doing some experimenting, but the message is still there. I'd just like to know what exactly it means maybe be pointed to a site that explains it so I can learn more about it. Will put in output of dmesg ifconfig below. Thanks for all replies. There's nothing wrong. It just mean SMBus is not supported. SMBus is a system management bus. It is generally used to read and control fans, temperature sensors and such. It is not supported on 3.8, but 3.9 will support a wide variety of SMBus controllers. Install 3.9-beta to take a look. It's available on the various mirrors. The ichiic(4) and iic(4) man pages contain some more info. You can read them via the web site: http://www.openbsd.org/cgi-bin/man.cgi?query=ichiic -Otto Thanks, Otto, for the reply. I'll try it. Have an old Prioris server donated from a friend to experiment on. Just checked in 3.8 and there's a man page for iic, leading eventually to other related stuff, including sensorsd and sysctl. I've played around with them a little, especially when I was having mobo problems. Thanks again. Denny White Please do not CC me. Already subscribed to mailing list. GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A iD8DBQFD2oQgy0Ty5RZE55oRAiSRAKCjCdr9zzEeOhW2wTFXnFkxmdCAfQCgm8/C Or3s0gbXXz5qsK+YVW8qT0w= =cM0J -END PGP SIGNATURE-
