[go: up one dir, main page]

Menu

#99 kernel exception for 5.1.4-i486 on K6-3 SIS630

Bering-uClibc 5.1.0
closed
nobody
None
no fix needed
2015-06-05
2015-04-20
Fred
No

I'm running Bering uClibc on a SIS630 (sis 5597, only 5595 is supported by kernel module for this motherboard so module is not loaded by the kernel). My current working version is 3.1.1 of Bering. I have tried to install 5.1.3 and now 5.1.4 but after a few pings or some network traffic, the system gives a kernel trap message and hangs. I haven't hooked up a serial console to catch messages yet but may try to if I have time this week. The processor is an AMD K6-3 with tulip and 8139too network cards.

Thank you,

Fred

Discussion

  • KP Kirchdörfer

    KP Kirchdörfer - 2015-04-22

    Yes, we need more information.

    pls also provide more system information (lsmod, lspci...)

    Did you try to run hwdetect to install modules needed?

     
  • Fred

    Fred - 2015-04-22

    I ran hwdetect to install modules. They seemed to load OK when I checked the dmesg output. Also ran lspci but I will need to capture it for you. I will do it when I have a serial console working. Hopefully over the weekend. Maybe sooner. Then I can have lsmod and lspci information for you as well.

    Cheers,

    Fred

     
  • Fred

    Fred - 2015-05-08

    Hi,

    I'm finally back to this. I built a custom kernel for amdk6 using the source for 5.1.4 and a diff of the i486 config patch. I only changed the processor type in the kernel configuration. Nothing else except for what would have been changed by the menuconfig for the linux kernel. When I ran the new kernel my machine stayed up much longer, ran faster and I was able to get some messages. Still doing the "sneakernet" thing with this though. Tomorrow or Sunday I will post logs, etc. here. The kernel exception complained about a ksoftirq. Anyway, it ran long enough to configure and check the system via the webconf tool. I thought that I should copy the page but didn't Oops!

    Cheers,

    Fred

     
  • Fred

    Fred - 2015-05-08

    Hi,

    Here are some messages. Notably, dmesg and lsmod. Still working on getting the kernel exception messages.

    Cheers,

    Fred

     
  • Fred

    Fred - 2015-05-09

    I think you can close this unless I find something with the 8139too module. I had a bad network card (8139too). I tried an Intel processor in place of the AMD and received the same kernel message. I then tracked the exception down to the network card and replaced it with a tulip based one and everything is running just fine now.

    I'll have to check on my build of the amdk6 kernel as it seems that I am missing some helper modules.

    Cheers,

    Fred

     
  • KP Kirchdörfer

    KP Kirchdörfer - 2015-06-05

    Thx for feedback.

     
  • KP Kirchdörfer

    KP Kirchdörfer - 2015-06-05
    • status: new --> closed
    • Resolution: --> no fix needed
     

Log in to post a comment.