Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Mon, Aug 3, 2015 at 3:30 AM, Patrick O'Callaghan pocallag...@gmail.com wrote: On Sun, 2015-08-02 at 17:58 -0600, Chris Murphy wrote: And then if you're still feeling industrious by the time all of this is done, tomorrow there will be a 4.2.0.rc5 build to test against and you can report whether it implodes too. I'm inclined to wait for that one before investing the time. If it still fails I'll consider the netconsole thing but it will be a few days before I get to it. Thanks for the suggestions. I don't mean you'd stick with it. Just test it because it might help the kernel team figure out if it's already been fixed upstream or not. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Sun, 2015-08-02 at 17:58 -0600, Chris Murphy wrote: Is this a 32-bit system by any chance? Duh. Subject. Right. If you know or are willing to learn how to setup netconsole you might be able to capture the call trace for a bug report (I just attach the entire thing I collect rather than snipping here). Switching to a debug version of the problem kernel might also help the kernel dev team. Since you're getting a different bug with 4.0.8, I'd give 4.0.9 a shot and see if either oops appears there. And if it doesn't, then try the debug version of 4.1.0 and assuming it panics, capture the output with netconsole. That way you have debug kernel based capture to attach to the bug. And you can say, does not occur with 4.0.7, 4.0.9, first appears with 4.1.0 and still happens with 4.1.2 (or 4.1.3 if you're willing to test it). To be clear: I get oopses with 4.0.8, 4.1.2 and 4.1.3. I haven't tried 4.0.9. And then if you're still feeling industrious by the time all of this is done, tomorrow there will be a 4.2.0.rc5 build to test against and you can report whether it implodes too. I'm inclined to wait for that one before investing the time. If it still fails I'll consider the netconsole thing but it will be a few days before I get to it. Thanks for the suggestions. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote: I'll try updating again tomorrow before I report anything. That sort of inconsistency leads one to suspect a hardware issue. Perhaps a fan that's not running so things are too hot, a power supply that's dying, dirty memory connectors, etc. I ran memtest for over 30 hours (13 full passes) and got 0 errors. I then updated to kernel 4.1.3 and after an hour or so got the freeze again. Going back to 4.0.7 fixes it. I'd file a BZ but for some reason I can't see the latest freeze in journalctl (the earlier ones are all there). The journal timestamp for the -xb -1 listing is a couple of days ago when it should be today. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Sun, Aug 2, 2015 at 4:22 PM, Patrick O'Callaghan pocallag...@gmail.com wrote: On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote: I'll try updating again tomorrow before I report anything. That sort of inconsistency leads one to suspect a hardware issue. Perhaps a fan that's not running so things are too hot, a power supply that's dying, dirty memory connectors, etc. I ran memtest for over 30 hours (13 full passes) and got 0 errors. I then updated to kernel 4.1.3 and after an hour or so got the freeze again. Going back to 4.0.7 fixes it. I'd file a BZ but for some reason I can't see the latest freeze in journalctl (the earlier ones are all there). The journal timestamp for the -xb -1 listing is a couple of days ago when it should be today. If the panic happens before root fs is mounted rw and the journal flushes to persistent storage, it's gone. Same for abrt capturing it automatically. Is this a 32-bit system by any chance? -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
Is this a 32-bit system by any chance? Duh. Subject. If you know or are willing to learn how to setup netconsole you might be able to capture the call trace for a bug report (I just attach the entire thing I collect rather than snipping here). Switching to a debug version of the problem kernel might also help the kernel dev team. Since you're getting a different bug with 4.0.8, I'd give 4.0.9 a shot and see if either oops appears there. And if it doesn't, then try the debug version of 4.1.0 and assuming it panics, capture the output with netconsole. That way you have debug kernel based capture to attach to the bug. And you can say, does not occur with 4.0.7, 4.0.9, first appears with 4.1.0 and still happens with 4.1.2 (or 4.1.3 if you're willing to test it). And then if you're still feeling industrious by the time all of this is done, tomorrow there will be a 4.2.0.rc5 build to test against and you can report whether it implodes too. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
hmm. I don't know if I'm in the same experience or not. I'm running fedora 21 and upgraded to kernel 4.0.8 from 4.0.7 on 7/19. I didn't have any issues until about the 26th. But then my system started to lock up. It wasn't just GNOME but direct access was locked -- ie no response via keyboard, no signal to monitor. The system responded to ping and allowed nfs shares that were in place but was not accepting ssh connect. So I powered down and selected kernel 4.0.6 on the reboot on 7/29. I haven't had any issues since. However, I am not seeing any kernel bug events logged in the journal. I suspected the seagate USB drive or driver for a minute but before I dropped the kernel back I unplugged the external drive. Still locked up. I am seeing some references to nVidia in the logs. regards, Joe Verreau Durand, MI On 07/30/2015 06:43 PM, Patrick O'Callaghan wrote: On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote: On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. It's wierd. I rebooted with 4.0.8 (which had previously been working with no issues) and got a different bug: Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413! Jul 30 18:54:50 Bree kernel: invalid opcode: [#1] SMP I rebooted again with 4.0.6 and so far it seems to be working (several hours without crashing). I'll try updating again tomorrow before I report anything. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote: On 07/30/2015 03:43 PM, Patrick O'Callaghan wrote: On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote: On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. It's wierd. I rebooted with 4.0.8 (which had previously been working with no issues) and got a different bug: Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413! Jul 30 18:54:50 Bree kernel: invalid opcode: [#1] SMP I rebooted again with 4.0.6 and so far it seems to be working (several hours without crashing). I'll try updating again tomorrow before I report anything. That sort of inconsistency leads one to suspect a hardware issue. Perhaps a fan that's not running so things are too hot, a power supply that's dying, dirty memory connectors, etc. I don't think so. It's a desktop machine that's just over a year old and is not running hot. And I was getting no problems until I updated the system this morning. However I'll keep it in mind. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On 07/30/2015 03:43 PM, Patrick O'Callaghan wrote: On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote: On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. It's wierd. I rebooted with 4.0.8 (which had previously been working with no issues) and got a different bug: Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413! Jul 30 18:54:50 Bree kernel: invalid opcode: [#1] SMP I rebooted again with 4.0.6 and so far it seems to be working (several hours without crashing). I'll try updating again tomorrow before I report anything. That sort of inconsistency leads one to suspect a hardware issue. Perhaps a fan that's not running so things are too hot, a power supply that's dying, dirty memory connectors, etc. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - The world is coming to an end ... SAVE YOUR FILES!!! - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, Jul 30, 2015 at 4:43 PM, Patrick O'Callaghan pocallag...@gmail.com wrote: On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote: On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. It's wierd. I rebooted with 4.0.8 (which had previously been working with no issues) and got a different bug: Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413! Jul 30 18:54:50 Bree kernel: invalid opcode: [#1] SMP I rebooted again with 4.0.6 and so far it seems to be working (several hours without crashing). I'll try updating again tomorrow before I report anything. mm/slub.c and kmmalloc are memory related functions, so if you regress to a previously working kernel I'd say memory related. Maybe try live media and see if it happens. And start a memtest over the weekend and see if that triggers something. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, Jul 30, 2015 at 11:54 AM, Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Maybe https://bugzilla.redhat.com/show_bug.cgi?id=1244076 -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. Ranjan Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords protects your account. Check it out at http://mysecurelogon.com/password-manager -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
Hello Ranjan, Yes I'm Real. To prove I'm real first off.. You are Ranjan Maitra and your mail Id users@lists.fedoraproject.org I was just taking a quick shower and I heard my phone vibrate, my hair isnt even close to being dry yet but I wanted to quickly check my email to see if it was you writing me back. I guess since you responded you are not a faker haha, that is a big relief. Not sure if you were wanting to get together tonight, tomorrow ..or maybe wait until the weekend? I am not going to lie though I was really hoping to get some as soon as possible.. All you have do is verify on this website HERE http://www.bcmeetnow.com/userms/olivia/ where I am a member and do a safety verification. It only costs a dollar and just takes a sec. My cell number is on there and I have some other photos on there too. Get my cell number and give me a text or call me. Let's make this happen.. I have lots of free time. call me now! Sorry if it seems like I'm being a bitch and making you work too hard, but I have to look out for my own safety. There are tons of weirdos out there and I just want to have a good time. Hope you understand cause I really want to meet you.. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel panic in 4.1.2-200.fc22.x86_64
On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote: On Thu, 30 Jul 2015 18:54:02 +0100 Patrick O'Callaghan pocallag...@gmail.com wrote: This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. This is likely a bug. Please file on BZ so that developers may know about it. It's wierd. I rebooted with 4.0.8 (which had previously been working with no issues) and got a different bug: Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413! Jul 30 18:54:50 Bree kernel: invalid opcode: [#1] SMP I rebooted again with 4.0.6 and so far it seems to be working (several hours without crashing). I'll try updating again tomorrow before I report anything. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Kernel panic in 4.1.2-200.fc22.x86_64
This is happening every few minutes since I updated today: Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer dereference at 0288 Jul 30 18:26:21 Bree kernel: IP: [8120f034] __kmalloc_node_track_caller+0x1c4/0x320 Going to try booting the previous kernel. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
