devel August 2010

devel@lists.centos.org

28 participants
15 discussions

wine 1.2 packages
by Janez Kosmrlj 12 Aug '10

12 Aug '10

Hi there, I made wine 1.2 packages for centos. I would like to share them but i don't have a public repository. Is there a place, where i could upload this packages. Maybe someone else would need them too. The packages are built to my needs, so they don't have winetricks or desktop integration, but they work. Regards Janez

3 4

centos site down?
by Akemi Yagi 09 Aug '10

09 Aug '10

I cannot connect to www.centos.org and related sites. It was noticed that access to the forums has been very slow today. Now the site is totally inaccessible. Akemi

3 7

rpms development
by Nickos H 09 Aug '10

09 Aug '10

Why centos does not have something similar like this: http://cvs.fedoraproject.org/viewvc/rpms/

5 9

Re: [CentOS-devel] [CentOS] WAS/CentOS 5.5 latest revisions seem really slow//Now Where are the Kernels?
by JohnS 04 Aug '10

04 Aug '10

On Wed, 2010-08-04 at 00:41 -0700, Mark wrote: > On Tue, Aug 3, 2010 at 9:30 PM, JohnS <jses27(a)gmail.com> wrote: > > > > You can do: > > rpm -q --changelog kernel >> changelog.log \ > > rpm -q --changelog kernel-2.6.18-194.8.1.el5 >> changelog.log > > > > To view the changelog for patches and BZs Applied to the kernel or any > > rpm. As in load up the newest one and run the command. I see a lot of > > changes between the newest one and the one (194.3.1) that you tried and > > said solved it. I would creep on up in versions to the newest one you > > can run with out the problem then file a bug report with a good > > description of the problem and type of hardware also (i think important > > for your problem). > > > > Egad - on the CentOS mirror I checked (USC), there are no kernels > between 194.3.1 and 194.8.1. Sun May 02 2010 Jiri Pirko <jpirko(a)redhat.com> [2.6.18-194.3.1.el5] Well that one you have. Why do you have it? Because I guess an @CentOS.org Hat decided to build that one while all the other ones were plain out skipped in-between? My ohh my the Heart and Soul was forgotten. All of 4 - FOUR of them. Effectively your stuck with the one you got that works or you have to learn to build your own from the red hat sources. > If I just build kernels from the Linux archives, would those just work > as-is under CentOS? I haven't actually done that in a while, but if > it's moderately safe using the "standard" spec files.... Maybe so be carefull. So insightfully what I do for my precious customers on CentOS is I actually build the updates from the RH Sources to keep them happy because some do like to plunder about when are updates coming out. Maybe the cache directory eatted them up? John

1 1

Linux NFSv4 Client (CentOS-5.3) kernel panic when running LTP
by Sid Moore 02 Aug '10

02 Aug '10

Hi, My NFS Client is CentOS5.3 (2.6.18) and server is SUSE11. When running LTP (ltp-full-20080930), the client crashed. the stack is below. Kernel BUG at fs/nfs/nfs4xdr.c:872 invalid opcode: 0000 [1] SMP last sysfs file: /block/sdb/size CPU 0 Modules linked in: ipv6 xfrm_nalgo crypto_api autofs4 hidp l2cap bluetooth blockvt(PU) nfs(U) lockd(U) fscache nfs_acl sunrpc ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi dm_mirror dm_multipath scsi_dh video hwmon backlight sbs i2c_ec button battery asus_acpi acpi_memhotplug ac lp floppy sg pcspkr i2c_piix4 i2c_core pcnet32 mii parport_pc parport shpchp serio_raw dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 18655, comm: mknod01 Tainted: P 2.6.18-128.el5 #1 RIP: 0010:[<ffffffff8844841d>] [<ffffffff8844841d>] :nfs:encode_share_access+0x6d/0x82 RSP: 0018:ffff81000d4cdb18 EFLAGS: 00010297 RAX: 00000000ffffffff RBX: ffff810007c770b8 RCX: ffff810007c770b8 RDX: 0000000000000008 RSI: 0000000000000008 RDI: ffff81000d4cdb68 RBP: 0000000000000080 R08: ffff810007c770ac R09: 0000000000000009 R10: ffff81000601e980 R11: ffffffff8844bc69 R12: ffff81000d4cdb68 R13: ffff81000216d158 R14: ffff81000d4cde18 R15: ffff810002912000 FS: 00002b7f2d2c3210(0000) GS:ffffffff803ac000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000003ec6a41900 CR3: 0000000007c10000 CR4: 00000000000006e0 Process mknod01 (pid: 18655, threadinfo ffff81000d4cc000, task ffff810004308040) Stack: ffff810004308040 ffff810007c770b0 ffff81000834f408 ffffffff8844b919 ffff8100080b7df8 ffff81000216d158 ffff81000834f408 ffffffff8844bc69 ffff81000216d158 ffffffff8844bcd6 ffff810007c770c0 ffff81000216d160 Call Trace: [<ffffffff8844b919>] :nfs:encode_open+0x66/0x33e [<ffffffff8844bc69>] :nfs:nfs4_xdr_enc_open+0x0/0xac [<ffffffff8844bcd6>] :nfs:nfs4_xdr_enc_open+0x6d/0xac [<ffffffff8844bc69>] :nfs:nfs4_xdr_enc_open+0x0/0xac [<ffffffff883c63f0>] :sunrpc:call_transmit+0x1bc/0x222 [<ffffffff883cb923>] :sunrpc:__rpc_execute+0x92/0x24e [<ffffffff883cbb36>] :sunrpc:rpc_run_task+0x37/0x3f [<ffffffff884430e0>] :nfs:_nfs4_proc_open+0x50/0x1aa [<ffffffff88443ff2>] :nfs:nfs4_do_open+0xc2/0x1dd [<ffffffff884459a4>] :nfs:nfs4_proc_create+0x7f/0x1b2 [<ffffffff883cc91a>] :sunrpc:rpcauth_lookup_credcache+0x12e/0x24c [<ffffffff8842d3c4>] :nfs:nfs_access_get_cached+0xab/0xfa [<ffffffff8842e440>] :nfs:nfs_create+0x87/0xed [<ffffffff8002221b>] d_alloc+0x174/0x1a9 [<ffffffff8003a031>] vfs_create+0xe6/0x158 [<ffffffff800e3120>] sys_mknodat+0x107/0x188 [<ffffffff8005d229>] tracesys+0x71/0xe0 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 0f 0b 68 14 5e 45 88 c2 68 03 c7 03 00 00 00 00 41 5a 5b 5d RIP [<ffffffff8844841d>] :nfs:encode_share_access+0x6d/0x82 RSP <ffff81000d4cdb18> <0>Kernel panic - not syncing: Fatal exception I think open_flags was set to be zero when calling encode_share_access(), but I don't know what happened and triggered this crash. is anyone willing to help me ? Best, sid

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2010