From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NyLac-0007w8-Fb for garchives@archives.gentoo.org; Sun, 04 Apr 2010 08:53:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8D73EE0BE1; Sun, 4 Apr 2010 08:53:11 +0000 (UTC) Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by pigeon.gentoo.org (Postfix) with ESMTP id 30F11E0BE1 for ; Sun, 4 Apr 2010 08:53:11 +0000 (UTC) Received: by bwz23 with SMTP id 23so384931bwz.26 for ; Sun, 04 Apr 2010 01:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=mR7e6O2o981dOQYQaO0PuFHwT0R7+Qd3TbXR9qmX/zg=; b=fyahm4KPOjk/LhmOzHj0ChHCzK0EUSTeFwgu8QG0/L3J4PBF7JpejY1DjThCUwV5eU QUwgWzfFwVsl8N7d2AarHo+2qQTadsRE5UNvvwbuRGLkKe//aFX5TIaMrtn7ADqj5BvG q8xj2RZnJ6p4mRk00LpMTc+lP6F/RfOszcERE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=PSvNoOB0NvWj92HxgxufhRr8YOoz9PRwhdJQvIMH33ZJ6SIp8ZJByBfQ0vWvfePPy/ g6Xw5qnpzMjjJbF807zl137sEngThKjrfKlbfFvFtQcmtFy5foLycaby/vz2DIAWtup4 T9fQRAXITlzbOkKKfIP4gtrTQcbxIgofQOVIQ= Received: by 10.204.11.22 with SMTP id r22mr1529880bkr.120.1270371189515; Sun, 04 Apr 2010 01:53:09 -0700 (PDT) Received: from (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id s17sm94765594bkd.4.2010.04.04.01.53.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 04 Apr 2010 01:53:08 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Disk or filesystem issue? Date: Sun, 4 Apr 2010 09:52:52 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.32-gentoo-r8; KDE/4.3.5; x86_64; ; ) References: <4BB6F768.5050102@jaftan.com.au> <201004030923.20108.michaelkintzios@gmail.com> <4BB7E2C1.2000407@jaftan.com.au> In-Reply-To: <4BB7E2C1.2000407@jaftan.com.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9494910.zp50BA07YL"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201004040953.06928.michaelkintzios@gmail.com> X-Archives-Salt: e288eae3-8b2b-4a41-bfca-e266f744647e X-Archives-Hash: 8f9edd8996e319ef4f3103ad870335f2 --nextPart9494910.zp50BA07YL Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sunday 04 April 2010 01:52:17 Adam wrote: > > Probably neither. Can you Ctrl+F12 to see what the logs are > > saying? I've been getting kernel Oops! on shutdown on one > > machine of mine with the 2.6.31-gentoo-r10 kernel. Might be > > similar >=20 > Ok, i found this, which is mentioning fglrx, and the problem may have > started when i changed driver versions. >=20 > So is it possible for an X driver to cause filesystem issues? I would > have assumed not. >=20 >=20 >=20 > Apr 4 10:38:08 sphinx shutdown[5768]: shutting down for system reboot > Apr 4 10:38:09 sphinx init: Switching to runlevel: 6 > Apr 4 10:38:09 sphinx gnome-session[5585]: WARNING: Detected that > screensaver has left the bus > Apr 4 10:38:09 sphinx gnome-keyring-daemon[5614]: dbus failure > unregistering from session: Connection is closed > Apr 4 10:38:09 sphinx su[5753]: pam_unix(su:session): session closed > for user root > Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1d.1: release dev 2 > ep81-INT, period 8, phase 4, 93 us > Apr 4 10:38:09 sphinx kernel: uhci_hcd 0000:00:1a.0: release dev 4 > ep81-INT, period 8, phase 4, 14 us > Apr 4 10:38:09 sphinx kernel: __ratelimit: 20 callbacks suppressed > Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in > preemptible [00000000] code: X/5275 > Apr 4 10:38:09 sphinx kernel: caller is KAS_GetExecutionLevel+0xd/0x120 > [fglrx] > Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P > 2.6.31-gentoo-r6 #4 > Apr 4 10:38:09 sphinx kernel: Call Trace: > Apr 4 10:38:09 sphinx kernel: [] ? > debug_smp_processor_id+0xd9/0xe0 > Apr 4 10:38:09 sphinx kernel: [] ? > KAS_GetExecutionLevel+0xd/0x120 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > MCIL_GetExecutionLevel+0x39/0x80 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > CallbackQueueAccess+0x2b/0x2a0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > UnRegisterIRQClient_Worker+0x0/0xe0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > MCIL_bMiniportCapEnabled+0x82/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > UnRegisterIRQClient+0x83/0xe0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > IRQMGR_IRQSourceSupported+0x7e/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > IRQMGR_Access+0x131/0x190 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > fireglAsyncioUnregisterIntMsgHandlers+0x2c3/0x3c0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > asyncIONotifyMsg+0x234/0x3e0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > firegl_asyncio_write+0x189/0x250 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? > ip_firegl_write+0x58/0xa0 [fglrx] > Apr 4 10:38:09 sphinx kernel: [] ? vfs_write+0xcb/0x180 > Apr 4 10:38:09 sphinx kernel: [] ? sys_write+0x53/0xa0 > Apr 4 10:38:09 sphinx kernel: [] ? > system_call_fastpath+0x16/0x1b > Apr 4 10:38:09 sphinx kernel: BUG: using smp_processor_id() in > preemptible [00000000] code: X/5275 > Apr 4 10:38:09 sphinx kernel: caller is > KCL_SPINLOCK_STATIC_Grab+0x25/0x110 [fglrx] > Apr 4 10:38:09 sphinx kernel: Pid: 5275, comm: X Tainted: P > 2.6.31-gentoo-r6 #4 > Apr 4 10:38:09 sphinx kernel: Call Trace: > Apr 4 10:38:09 sphinx kernel: [] ? > debug_smp_processor_id+0xd9/0xe0 It could be that this kernel does not play well with fglrx? I would unmask= =20 the next kernel up the tree and try that out. This particular kernel versi= on=20 you are running had a few bugs hanging around, which may affect your proble= m. PS. My machine that keeps crashing on shutdown doesn't always crash at=20 exactly the same point - but it is well after X has been stopped and=20 invariably after the fs has been unmounted. PPS. Clutching at straws, but just for testing purposes you may want to bo= ot=20 with no X, just on a console and try shuting down from there? =2D-=20 Regards, Mick --nextPart9494910.zp50BA07YL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEABECAAYFAku4U3IACgkQVTDTR3kpaLYZMACfXeOfot/q7Ot5keF1Kv/meOC7 9qcAoKsOyii/fgesuFKbmhCnYguC/Qz5 =NqKZ -----END PGP SIGNATURE----- --nextPart9494910.zp50BA07YL--