Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  Kernel panic after d-u  (Read 5638 times)

eQuacky

  • Guest
Re: Kernel panic after d-u
« Reply #15 on: 2016/06/28, 21:27:14 »
Can you other guys tell your wlan chipset?

Network:   Card-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter                                                                                                           
driver: rtl8192ce port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8176                                                                                             
IF: wlan0 state: up mac: 60:d8:19:c1:f3:23                                                                                                                   
Card-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet 
driver: atl1c v: 1.0.1.1-NAPI port: 2000 bus-ID: 02:00.0 chip-ID: 1969:1083                                                                                 
IF: eth0 state: down mac: 04:7d:7b:08:9b:c3                                                                                                                 
WAN IP: 46.223.119.170 IF: eth0 ip-v4: N/A ip-v6: N/A                                                                                                       
IF: wlan0 ip-v4: 192.168.1.9 ip-v6: fe80::62d8:19ff:fec1:f323


eQuacky

  • Guest
Re: Kernel panic after d-u
« Reply #16 on: 2016/06/28, 21:40:47 »
please give us the output of -> inxi -bCn and -> /sbin/ifconfig -a

ltq@sid-X121e:~$ inxi -bCn
System:    Host: sid-X121e Kernel: 4.5.6-towo.1-siduction-amd64 x86_64 (64 bit)
                 Desktop: LXQt                                                         
                 Distro: siduction 14.1.0 Indian Summer - kde - (201411230337)         
Machine:   System: LENOVO (portable) product: 30515YG v: ThinkPad X121e           
                 Mobo: LENOVO model: 30515YG                                           
                 Bios: LENOVO v: 8RET30WW (1.12 ) date: 09/15/2011                     
Battery     BAT1: charge: 52.6 Wh 97.0% condition: 54.2/62.2 Wh (87%)             
CPU:         Dual core AMD E-450 APU with Radeon HD Graphics (-MCP-) cache: 1024 KB
                 clock speeds: max: 1650 MHz 1: 1320 MHz 2: 825 MHz                     
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6320]       
                 Display Server: X.Org 1.18.3 drivers: (unloaded: fbdev,vesa)           
                 Resolution: 1366x768@60.02hz                                           
                 GLX Renderer: Gallium 0.4 on AMD PALM (DRM 2.43.0, LLVM 3.8.0)         
                 GLX Version: 3.0 Mesa 11.2.2                                           
Network:   Card-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce   
                  IF: wlan0 state: up mac: 60:d8:19:c1:f3:23                             
                 Card-2: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet driver: atl1c   
                  IF: eth0 state: down mac: 04:7d:7b:08:9b:c3                           
Drives:       HDD Total Size: 320.1GB (56.1% used)                                   
Info:           Processes: 170 Uptime: 1 day Memory: 1525.3/3555.1MB                   
                  Client: Shell (bash) inxi: 2.3.0

ltq@sid-X121e:~$ /sbin/ifconfig -a                                       
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
         ether 04:7d:7b:08:9b:c3  txqueuelen 1000  (Ethernet)
         RX packets 0  bytes 0 (0.0 B)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 0  bytes 0 (0.0 B)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 178  bytes 14567 (14.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 178  bytes 14567 (14.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.1.9  netmask 255.255.255.0  broadcast 192.168.1.255
            inet6 fe80::62d8:19ff:fec1:f323  prefixlen 64  scopeid 0x20<link>
            ether 60:d8:19:c1:f3:23  txqueuelen 1000  (Ethernet)
            RX packets 111900  bytes 109223474 (104.1 MiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 96099  bytes 14889440 (14.1 MiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

campitosai

  • Guest
Re: Kernel panic after d-u
« Reply #17 on: 2016/06/28, 23:40:08 »
please give us the output of -> inxi -bCn and -> /sbin/ifconfig -a

campi@siductionldlc:~$  inxi -bCn
System:    Host: siductionldlc Kernel: 4.5.4-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: Gnome 3.20.2
           Distro: siduction 13.2.1 December - gnome - (201401272112)
Machine:   System: CLEVO (portable) product: C4100/C5100
           Mobo: CLEVO model: C4100/C5100 Bios: Phoenix v: 1.01.11 date: 10/15/2010
Battery    BAT0: charge: 21.0 Wh 88.8% condition: 23.6/44.0 Wh (54%)
CPU:       Dual core Celeron T3300 (-MCP-) cache: 1024 KB
           clock speeds: max: 1994 MHz 1: 1994 MHz 2: 1994 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
           Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@59.99hz
           GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1 Mesa 11.2.2
Network:   Card-1: Realtek RTL8191SEvB Wireless LAN Controller driver: rtl8192se
           IF: wlan0 state: up mac: 48:5d:60:6e:4a:63
           Card-2: JMicron JMC260 PCI Express Fast Ethernet Controller driver: jme
           IF: eth0 state: down mac: 00:90:f5:ad:6e:b4
Drives:    HDD Total Size: 120.0GB (67.0% used)
Info:      Processes: 162 Uptime: 15 min Memory: 974.1/3891.3MB Client: Shell (bash) inxi: 2.3.0

campi@siductionldlc:~$ /sbin/ifconfig -a
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:90:f5:ad:6e:b4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 30 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Boucle locale)
        RX packets 3  bytes 147 (147.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3  bytes 147 (147.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.187  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::4a5d:60ff:fe6e:4a63  prefixlen 64  scopeid 0x20<link>
        ether 48:5d:60:6e:4a:63  txqueuelen 1000  (Ethernet)
        RX packets 11350  bytes 12414535 (11.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5924  bytes 597161 (583.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Thank you

campitosai

  • Guest
Re: Kernel panic after d-u
« Reply #18 on: 2016/07/14, 14:12:54 »
Hello,

always same problem with kernel 4.6.4-towo. Here is the picture of the "kernel panic" screen.
It seems to be a wpa_supplicant problem ?

Thanks for your help !

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.920
Re: Kernel panic after d-u
« Reply #19 on: 2016/07/14, 14:32:40 »
Try kernel 4.7-rc7 from our experimental, if the issue is gone, write a bugreport to kernel bugzilla.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

campitosai

  • Guest
Re: Kernel panic after d-u
« Reply #20 on: 2016/07/17, 17:25:52 »
Try kernel 4.7-rc7 from our experimental, if the issue is gone, write a bugreport to kernel bugzilla.

Hi Towo,

I tried 4.7-rc7 kernel and the problem disappeared.
Here is the bugreport to kernel bugzilla :
https://bugzilla.kernel.org/show_bug.cgi?id=135441

Thank you

Offline vilde

  • User
  • Posts: 708
Re: Kernel panic after d-u
« Reply #21 on: 2016/08/11, 16:57:39 »
Today I installed "linux-image-4.7.0-towo.1-siduction-amd64" and the computer boots normally. That means that for me this issue is solved with the new kernel from towo.

As I have red that there is a bugreport  about this issue I will not make this thread as solved. If somebody else (like towo) or administrator will mark this as solved you shall do that.