[CentOS] Kernel Panic on HP/Compaq ProLiant G7
Hello Everyone, I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was no video on the console (or remote console via iLO). It would not reboot or cold boot through iLO, I actually had to hold the power to turn it off and then hit it again to power up. This happened several times within a few days of each other. Each time, there was no evidence in any logs of a problem - the system just seemed to stop or lock up. We did have a CPU problem light appear on the front, so HP came in and replaced the one 4-core CPU. Since then, it has run as long as two weeks, but still crashes randomly. After the last reboot, I left the console in text mode on vt1, and when it crashed again this morning this was displayed on the screen: CS: 0010 DS: ES: CR0: 80050033 CR2: 8100dc435cf0 CR3: 8a6ca000 CR4: 06e0 Process smbd (pid: 18970, threadinfo 81001529e000, task 81011f5347a0) Stack: 81011e4e71c0 8100cf12a015 80009c41 81011e4e71c0 0001 00030027ea9d 8100cf12a011 81011e4e71c0 81010d9cf300 81011e4e71c0 8101044099c0 Call Trace: [] __link_path_walk+0x3a6/0xf5b [] link_path_walk+0x42/0xb2 [] do_path_lookup+0x275/0x2f1 [] getname+0x15b/0x1c2 [] __user_walk_fd+0x37/0x4c [] vfs_stat_fd+0x1b/0x4a [] fcntl_setlk+0x243/0x273 [] sys_newstat+0x19/0x31 [] tracesys+0x71/0xe0 [] tracesys+0xd5/0xe0 Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc RIP [] RSP CR2: 8100dc435cf0 <0>Kernel panic - not syncing: Fatal exception This suggests that something happened in a Samba process. I have the Samba3x packages installed since we are beginning to introduce Win7 clients into our environment. Googling "Kernel panic - not syncing: Fatal exception" and "CentOS" produced many hits, but nothing that seemed to exactly match my problem. Since this is the only G7 server I have here right now, I can't reproduce the problem on another machine. The G6s I have running the identical version of CentOS have no problems. I am trying to determine if this is pointing to a hardware or software issue. Some of the Google results suggested using a Centosplus kernel - is this a good idea? The server is a HP DL380 G7 Server with 4 GB RAM (1 DIMM 1333 MHz), one 4-core CPU (2133 MHz), 4 built-in Broadcom "NetExtreme II BCM5709 II Gigabit Ethernet" NICs, and a P410 Smart Array Controller. The P410 and the system BIOS have both been updated to the latest levels to see if that fixes the crashes, with no change. Any idea where I should look next? Thanks for any help anyone can provide! Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us Tel: 1 (864) 260-8459 Fax: 1 (864) 260-8422 dave.wind...@us.bosch.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] FYI - pci_mmcfg_init kernel error after upgrading to 5.6
Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable." Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933 There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on If everyone is already familiar with this, please ignore. :-) -- Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us Tel: 1 (864) 260-8459 Fax: 1 (864) 260-8422 dave.wind...@us.bosch.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FYI - pci_mmcfg_init kernel error after upgrading to 5.6
On 4/25/2011 10:26 AM, Johnny Hughes wrote: > On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote: >> Just thought I'd pass along an error I received this weekend after >> upgrading two servers to 5.6. Both are HP Proliant DL380 servers >> running 64-bit, but one is a G6 model and one is a G7. After the >> upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers >> displayed the following error at boot: >> "pci_mmcfg_init marking 256MB space uncacheable." >> >> Some Googling found me the following link: >> https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933 >> >> There are apparently performance implications due to this issue. >> Fortunately, the solution is simple: just boot with the kernel parameter >> acpi_mcfg_max_pci_bus_num=on >> >> If everyone is already familiar with this, please ignore. :-) >> > > Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D > > https://bugzilla.redhat.com/show_bug.cgi?id=581933 > > However, the advise is good regardless of version of kernel. > Yes, I saw the reference to RHEL 5.5 in the bug description, but I never saw the message before the upgrade to CentOS 5.6. Hardware differences, I guess. The bug description mentions a Dell Precision. Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FYI - pci_mmcfg_init kernel error after upgrading to 5.6
On 4/25/2011 5:15 PM, Johnny Hughes wrote: > On 04/25/2011 10:19 AM, Ned Slider wrote: >> On 25/04/11 15:44, Windsor Dave L. (AdP/TEF7.1) wrote: >> >> I saw and reported the issue during QA for CentOS-5.6. >> >> I think it's quite widespread, I saw it on generic Intel-based motherboards. >> >> I've not had any issues applying the documented "fix" and have been >> running that since January. > > Well if this is wipe spread then we need to add this to the Release > Notes too ... I'll take care of that if it is not already there. > I looked in the 5.6 Release Notes on the Wiki and didn't see it under "Known Problems" or anywhere else. Thanks! Best Regards, Dave Windsor ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Archive mail format?
On 11/2/2011 4:42 PM, Les Mikesell wrote: > On Wed, Nov 2, 2011 at 2:23 PM, Ljubomir Ljubojevic wrote: >> Vreme: 11/02/2011 07:53 PM, Phoenix, Merka piše: > I have a bunch of old mail spread variously across dovecot maildirs and > mbox format files on several machines that are headed for the trash. Is > there anything considered to be a portable archive format for mail > messages, and if so are there tools to copy into it - or do I have to > pick a client and copy to its local storage?<< > > -- >>> The mbox format and mail messages in the dovecot maildirs can be copied as >>> is to another server (or directory). >>> The only thing that you don't need (or probably don't want) to copy would >>> be the index files that live in the directory above the maildirs. >>> >>> The index files are in the form: dovecot-* and dovecot.index* and usually >>> live above the actual directory where the messages are stored. Also, most >>> of the sub-folders have a leading '.' so would be "hidden" unless you use >>> 'ls -la' to view the directory contents. >>> >> >> There is simple script to convert maildir to mailbox format: >> http://www.linuxquestions.org/questions/linux-general-1/a-script-to-convert-maildir-to-mailbox-format-381568/ >> >> and scripts to convert mailbox to maildir: >> http://batleth.sapienti-sat.org/projects/mb2md/ >> http://perfectmaildir.home-dn.net/ >> >> There are many more, but this ones come at the top of the google search. > > Thanks - I think most of what I'd want to keep is still accessible via > imap. What I'm wondering is if there is a general consensus about > the file format for long term storage that would be most likely to > permit direct search and access from some future mail reader, possibly > on some other OS. I suppose I could make a VM image that I could fire > up as an imap server again, but that seems kind of cumbersome. > If you are interested in local storage readable on multiple platforms then mbox format can be useful. There are many Linux/UNIX clients that can read it, and so can MSWin clients like Thunderbird. Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] find most recent file update in directory
On 12/9/2011 9:27 AM, John R. Dennison wrote: > On Fri, Dec 09, 2011 at 03:15:53PM +0100, Mogens Kjaer wrote: >> >> Try something like: >> >> find . -type f -printf '%A@ %p\n' | sort -n | tail -1 > > I believe you want %T@ instead of %A@ (modification time versus access > time). I would also suggest sort -nr to sort from most recent to least > recent. > > > John I like: find . -type f -printf '%TY/%Tm/%Td %TH:%TM:%TS %p\n' | sort -n | tail -1 which shows the last access date/time in a human-readable format that also sorts nicely (/MM/DD HH:MM:SS). Note that some distros include fractional values with the seconds (%TS), making it even more accurate. My CentOS 5.7 server does not, my Kubuntu 11.10 desktop does. Best Regards, Dave Windsor Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) Anderson, SC USA ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
