View previous topic :: View next topic |
Author |
Message |
jagdpanther l33t
Joined: 22 Nov 2003 Posts: 729
|
Posted: Wed Nov 07, 2012 7:46 pm Post subject: vanilla-source kernel 3.6.5 and 3.6.6 crash at end of boot |
|
|
I am getting a "general protection fault" after boot when my Gentoo system uses either Linux (vanilla-source) 3.6.5 or 3.6.6 but 3.6.4 works without issue. I am using the same configuration file (just using 'make oldconfig; make -j13; make modules_install to build each kernel.)
Below is the end of the boot where the 'general protecton fault' occurs.
Any suggestions on how fix this? Should I post this request on a different forum?
Thanks
------------
Code: |
Nov 6 18:51:02 runner xinetd[3554]: removing time
Nov 6 18:51:02 runner xinetd[3554]: removing time
Nov 6 18:51:02 runner xinetd[3554]: xinetd Version 2.3.15 started with libwrap loadavg options compiled in.
Nov 6 18:51:02 runner xinetd[3554]: Started working: 2 available services
Nov 6 18:51:02 runner kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov 6 18:51:05 runner ntpd[3329]: Deleting interface #6 eth0, fe80::4a5b:39ff:fe62:8fa#123, interface stats: received=0, sent=0, dropped=0, active_time=8 secs
Nov 6 18:51:05 runner ntpd[3329]: peers refreshed
Nov 6 18:51:10 runner kernel: general protection fault: 0000 [#1] SMP
Nov 6 18:51:10 runner kernel: Modules linked in: xt_recent xt_tcpudp xt_LOG xt_limit xt_state ipt_MASQUERADE iptable_nat iptable_filter nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack ip_tables x_tables ipv6 hid_generic usbhid hid snd_pcm_oss snd_mixer_oss usblp keyspan usbserial snd_hda_codec_hdmi sr_mod cdrom sg uhci_hcd ehci_hcd xhci_hcd coretemp crc32c_intel ghash_clmulni_intel aesni_intel ablk_helper asus_atk0110 cryptd snd_hda_codec_realtek aes_x86_64 aes_generic usbcore sky2 i2c_i801 pcspkr hwmon snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_alloc usb_common
Nov 6 18:51:10 runner kernel: CPU 0
Nov 6 18:51:10 runner kernel: Pid: 3705, comm: myhlt Not tainted 3.6.6-rr01 #1 System manufacturer System Product Name/P6X58D PREMIUM
Nov 6 18:51:10 runner kernel: RIP: 0010:[<ffffffffa01cfa4c>] [<ffffffffa01cfa4c>] keyspan_open+0x11c/0x190 [keyspan]
Nov 6 18:51:10 runner kernel: RSP: 0018:ffff880622fefa68 EFLAGS: 00010246
Nov 6 18:51:10 runner kernel: RAX: 0000000000000000 RBX: ffff880622e13a00 RCX: 0000000000000000
Nov 6 18:51:10 runner kernel: RDX: 0000000000000000 RSI: 0000000021bca410 RDI: 0000000000002580
Nov 6 18:51:10 runner kernel: RBP: ffff880622fefab8 R08: 0000000000000000 R09: 0000000000000003
Nov 6 18:51:10 runner kernel: R10: ffff88062186a480 R11: 0000000000000000 R12: 0000000000000cbd
Nov 6 18:51:10 runner kernel: R13: ffff880621b5d000 R14: 0000000000002580 R15: ffff880625b32800
Nov 6 18:51:10 runner kernel: FS: 00007f9de2ee7700(0000) GS:ffff88063fc00000(0000) knlGS:0000000000000000
Nov 6 18:51:10 runner kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 6 18:51:10 runner kernel: CR2: 00000000018e7048 CR3: 0000000607876000 CR4: 00000000000007f0
Nov 6 18:51:10 runner kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 6 18:51:10 runner kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 6 18:51:10 runner kernel: Process myhlt (pid: 3705, threadinfo ffff880622fee000, task ffff880622cdcd10)
Nov 6 18:51:10 runner kernel: Stack:
Nov 6 18:51:10 runner kernel: ffff88061ea9ef40 ffff880625b32800 0300880625b32ca8 ffff88062186a480
Nov 6 18:51:10 runner kernel: ffff88061ea9ef40 ffff880621b5bb68 ffff880621b5d008 ffff880625b32800
Nov 6 18:51:10 runner kernel: ffff880621b5bb00 ffff880621b5d000 ffff880622fefb08 ffffffffa01bf645
Nov 6 18:51:10 runner kernel: Call Trace:
Nov 6 18:51:10 runner kernel: [<ffffffffa01bf645>] serial_activate+0x75/0xa0 [usbserial]
Nov 6 18:51:10 runner kernel: [<ffffffff8129b027>] tty_port_open+0x87/0xd0
Nov 6 18:51:10 runner kernel: [<ffffffffa01bfc2a>] serial_open+0x3a/0x70 [usbserial]
Nov 6 18:51:10 runner kernel: [<ffffffff8129315c>] tty_open+0x29c/0x600
Nov 6 18:51:10 runner kernel: [<ffffffff812d51a4>] ? kobj_lookup+0x104/0x160
Nov 6 18:51:10 runner kernel: [<ffffffff810dfbd0>] chrdev_open+0xa0/0x180
Nov 6 18:51:10 runner kernel: [<ffffffff810dfb30>] ? cdev_put+0x30/0x30
Nov 6 18:51:10 runner kernel: [<ffffffff810da106>] do_dentry_open.clone.18+0x206/0x280
Nov 6 18:51:10 runner kernel: [<ffffffff810da19d>] finish_open+0x1d/0x30
Nov 6 18:51:10 runner kernel: [<ffffffff810ea44e>] do_last+0x76e/0xe30
Nov 6 18:51:10 runner kernel: [<ffffffff810e723c>] ? link_path_walk+0x8c/0x9a0
Nov 6 18:51:10 runner kernel: [<ffffffff810a5adf>] ? release_pages+0x1bf/0x210
Nov 6 18:51:10 runner kernel: [<ffffffff810eabbe>] path_openat+0xae/0x4e0
Nov 6 18:51:10 runner kernel: [<ffffffff810b750f>] ? tlb_flush_mmu+0x5f/0xa0
Nov 6 18:51:10 runner kernel: [<ffffffff810eb344>] do_filp_open+0x44/0xa0
Nov 6 18:51:10 runner kernel: [<ffffffff810f6ea7>] ? alloc_fd+0x47/0x130
Nov 6 18:51:10 runner kernel: [<ffffffff810dafb5>] do_sys_open+0x105/0x1f0
Nov 6 18:51:10 runner kernel: [<ffffffff810db0bc>] sys_open+0x1c/0x20
Nov 6 18:51:10 runner kernel: [<ffffffff813ce562>] system_call_fastpath+0x16/0x1b
Nov 6 18:51:10 runner kernel: Code: 08 e8 b9 86 0c e1 41 89 c6 85 c0 78 2d 44 0f b6 4d c7 0f b6 45 c6 4c 8b 55 c8 41 29 c1 45 31 c0 31 c9 31 d2 41 8b 72 68 44 89 f7 <41> ff 52 60 85 c0 75 07 44 89 b3 88 01 00 00 44 89 e0 c1 e8 1f
Nov 6 18:51:10 runner kernel: RIP [<ffffffffa01cfa4c>] keyspan_open+0x11c/0x190 [keyspan]
Nov 6 18:51:10 runner kernel: RSP <ffff880622fefa68>
Nov 6 18:51:10 runner kernel: ---[ end trace accb6e362c397b1a ]---
|
|
|
Back to top |
|
|
toralf Developer
Joined: 01 Feb 2004 Posts: 3922 Location: Hamburg
|
Posted: Wed Nov 07, 2012 8:08 pm Post subject: Re: vanilla-source kernel 3.6.5 and 3.6.6 crash at end of bo |
|
|
jagdpanther wrote: | Should I post this request on a different forum? | Yes.
Mail it to Linux Kernel <linux-kernel@vger.kernel.org> |
|
Back to top |
|
|
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
|
Back to top |
|
|
toralf Developer
Joined: 01 Feb 2004 Posts: 3922 Location: Hamburg
|
Posted: Thu Nov 08, 2012 7:05 pm Post subject: |
|
|
kernelOfTruth wrote: | do you - by chance - have a serial-ata drive connected to an usb-connector/adapter ?
if not best bet would be to remove that device from kernel configuration and re-compile the kernel | why does a plugged in device affects the compilation ? |
|
Back to top |
|
|
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
Posted: Thu Nov 08, 2012 9:25 pm Post subject: |
|
|
toralf wrote: | kernelOfTruth wrote: | do you - by chance - have a serial-ata drive connected to an usb-connector/adapter ?
if not best bet would be to remove that device from kernel configuration and re-compile the kernel | why does a plugged in device affects the compilation ? |
don't know
the error is referring to the adapter - so I thought if he doesn't have that adapter in use (whether via usb or on the mainboard) but enabled it in the kernel configuration - removing it from config and compiling the kernel without its driver would help as a quickfix - when the box is needed for work
as long as that general protection error doesn't impacts functionality leave it in ... _________________ https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa
Hardcore Gentoo Linux user since 2004 |
|
Back to top |
|
|
Tolstoi l33t
Joined: 20 May 2004 Posts: 678
|
Posted: Wed Nov 21, 2012 7:37 am Post subject: |
|
|
Got a similar message when I want to shut down my laptop. Have to power it off with the button then because it hangs. |
|
Back to top |
|
|
jagdpanther l33t
Joined: 22 Nov 2003 Posts: 729
|
Posted: Sun Nov 25, 2012 5:52 pm Post subject: |
|
|
I figured out what the problem was. I have two programs I wrote that connect to serial devices via the Keyspan usb to 4-serial-ports. When the driver was called a GPF occurred. I started up the programs at boot time so I originally thought it was a boot issue.
I sent the information to linux-kernel@vger.kernel.org and was promptly sent back a patch to
drivers/usb/serial/keyspan.c and was told there was an error in a source code commit in the latest kernels and a subsistent patch will correct the issue.
The patch works. (I just have to remember to add the patch to the vanilla-sources until the patch hits kernel.org.) |
|
Back to top |
|
|
|