You are not logged in.

#1 2012-10-24 01:38:54

Kebertx
Member
Registered: 2012-01-02
Posts: 69

[SOLVED] Kernel Panics made me cry.

rtl8180_init:Error channel plan! Set to default.

That's the only "Error" I could grep out of my dmesg log, I should have snapped a picture.

I had three kernel panics earlier today (this is after two panics on the 18th), the result of which has been a lot of worry, and a few manly tears during a physics lecture.

I was getting random kernel panics on the 3.5 kernel, but they went away after I blacklisted btusb (no clue why, didn't care tbqh). Now it seems my worries from the days of this thread are back.

To be frank, I have absolutely no clue how to deal with kernel panics, they just make me incredibly anxious and scared. And they are happening entirely too frequent for me to handle. I need someone to help me help myself. I need to know what is wrong so I can fix it and leave behind my fears that my system is unstable. What do I look for? What do I do? Should I just downgrade?

ALSO, I tried linux-lts, It throws me a million and one errors having to do with btrfs, so I switched back to the 3.6 kernel. I don't have the old package in /var/cache. Should I just give up on life, move to debian stable, and quietly weep?

Last edited by Kebertx (2012-10-24 15:29:28)

Offline

#2 2012-10-24 03:00:35

twelveeighty
Member
Registered: 2011-09-04
Posts: 1,456

Re: [SOLVED] Kernel Panics made me cry.

Maybe I'm feeding a troll here, but can you give us some facts instead of emotional issues? Was this system ever running fine? What happened since? Is this from a pacman update, hardware change?

Offline

#3 2012-10-24 05:27:58

Kebertx
Member
Registered: 2012-01-02
Posts: 69

Re: [SOLVED] Kernel Panics made me cry.

Sorry, I'm not trolling. Just baffled, really.

No hardware changes. I upgraded to the 3.6 kernel about a week ago, which seems to have brought back an issue of seemingly random kernel panics. By random, I mean that I can't find a logical connection between them. I'll be connecting to a wireless network, waking up my computer from suspend, unplugging it from it's charger, or not doing anything at all, and every once in a while one of these things apparently confuses my system and I get a panic. Three times today, the day after I switched from initscripts to systemd, Twice five days ago before I changed. I don't think that upgrade is related.

I found some pictures I took on the 18th. This probably isn't the best way to present information, but...
tZzA0ZA
tZzA0Yw
tZzA0Yg

I see "try_to_wake_up" in the error mess, as well as references to [r8187se], which is my wireless driver. I don't know what to do with any of the information it's given me, though. Ideas?

Offline

#4 2012-10-24 05:47:35

Stebalien
Member
Registered: 2010-04-27
Posts: 1,239
Website

Re: [SOLVED] Kernel Panics made me cry.

When something says "kernel BUG at ..." it's generally a kernel bug wink. Please report it upstream (bugzilla.kernel.org) and include those pictures.

Last edited by Stebalien (2012-10-24 05:47:50)


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C

Offline

#5 2012-10-24 09:33:28

Lekensteyn
Member
From: Netherlands
Registered: 2012-06-19
Posts: 192
Website

Re: [SOLVED] Kernel Panics made me cry.

"Tainted: G C" and "r8187se(C)"

The C taint flag means that the kernel is marked as "tainted crap" by the r8187se module. This flags is set for modules in the staging directory. Between 10 April 2010 and now, there are only changes to coding style, comments, small kernel API changes and other trivial errors. I think this module is pretty unmaintained. Maybe there is a different driver you can use?

Offline

#6 2012-10-24 15:28:33

Kebertx
Member
Registered: 2012-01-02
Posts: 69

Re: [SOLVED] Kernel Panics made me cry.

Lekensteyn wrote:

"Tainted: G C" and "r8187se(C)"

The C taint flag means that the kernel is marked as "tainted crap" by the r8187se module. This flags is set for modules in the staging directory. Between 10 April 2010 and now, there are only changes to coding style, comments, small kernel API changes and other trivial errors. I think this module is pretty unmaintained. Maybe there is a different driver you can use?

Sure enough... I went out and found this. RTL8187SE is listed under unsupported chips, and it links users here, which is "the vendor driver converted to compile with a 2.6.29, or later, kernel." I'm now fairly certain it's my wireless card.

Upon failing to make this work, I suppose I could install ndiswrapper and download the non-free driver that all the Windozers are using (still better than Debian).

I filed a bug report, and found lots of internet info about this wireless bug, which is all I really wanted. I guess I'll mark this solved. Thanks Arch people!

Offline

Board footer

Powered by FluxBB