Forum › Forums › New users › New Users and General Questions › kernel errors bug or bad hardware?
Tagged: call trace, kern.log
- This topic has 2 replies, 2 voices, and was last updated Nov 23-4:16 pm by galen.
Viewing 3 posts - 1 through 3 (of 3 total)
-
AuthorPosts
-
November 20, 2018 at 11:48 am #13541Member
galen
$ inxi -S System: Host: antix4400 Kernel: 4.9.126-antix.1-amd64-smp x86_64 bits: 64 Desktop: JWM 2.3.6 Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 aviator@antix4400:~ $ inxi -M Machine: Type: Laptop System: Hewlett-Packard product: HP Compaq nc4400 (RH018EC#ABA) v: F.0B serial: <root required> Mobo: Hewlett-Packard model: 30B1 v: KBC Version 59.35 serial: <root required> BIOS: Hewlett-Packard v: 68YHV Ver. F.0B date: 07/13/2007 [ 11.932501] ------------[ cut here ]------------ [ 11.932559] WARNING: CPU: 1 PID: 113 at drivers/gpu/drm/i915/intel_fbdev.c:414 intel_fb_initial_config+0x404/0x600 [i915] [ 11.932560] WARN_ON(!connector->state->crtc) [ 11.932562] Modules linked in: [ 11.932563] joydev i915 evdev input_leds snd_hda_codec_si3054 arc4 pcmcia snd_hda_codec_analog snd_hda_codec_generic serio_raw iwl3945 snd_hda_intel lpc_ich iwlegacy mac80211 snd_hda_codec snd_hda_core cfg80211 drm_kms_helper snd_hwdep drm fb_sys_fops syscopyarea tifm_7xx1 yenta_socket sysfillrect sysimgblt pcmcia_rsrc tifm_core rng_core snd_pcm snd_timer snd soundcore i2c_algo_bit pcmcia_core i2c_core intel_agp smsc_ircc2 irda hp_accel lis3lv02d input_polldev rfkill intel_gtt tpm_infineon parport_pc wmi battery parport shpchp acpi_cpufreq video ac button btrfs xor raid6_pq psmouse sdhci_pci sdhci mmc_core fan thermal fjes tg3 ptp pps_core [ 11.932632] CPU: 1 PID: 113 Comm: kworker/u4:6 Tainted: G W 4.9.126-antix.1-amd64-smp #1 [ 11.932634] Hardware name: Hewlett-Packard HP Compaq nc4400 (RH018EC#ABA)/30B1, BIOS 68YHV Ver. F.0B 07/13/2007 [ 11.932638] Workqueue: events_unbound async_run_entry_fn [ 11.932641] 0000000000000000 ffffffff813ebd72 ffffc90000c73bd8 0000000000000000 [ 11.932647] ffffffff81065c49 0000000000000001 ffffc90000c73c30 0000000000000004 [ 11.932652] ffff8800bae6f800 ffff880035de5a00 0000000000000000 ffffffff81065cca [ 11.932657] Call Trace: [ 11.932661] [<ffffffff813ebd72>] ? dump_stack+0x5c/0x7a [ 11.932665] [<ffffffff81065c49>] ? __warn+0xb9/0xe0 [ 11.932668] [<ffffffff81065cca>] ? warn_slowpath_fmt+0x5a/0x80 [ 11.932724] [<ffffffffa0709d34>] ? intel_fb_initial_config+0x404/0x600 [i915] [ 11.932729] [<ffffffff811ba451>] ? __kmalloc+0x1b1/0x1e0 [ 11.932736] [<ffffffffa040d904>] ? drm_setup_crtcs+0x1e4/0x9c0 [drm_kms_helper] [ 11.932742] [<ffffffffa040e3be>] ? drm_fb_helper_initial_config+0xce/0x460 [drm_kms_helper] [ 11.932797] [<ffffffffa070a49f>] ? intel_fbdev_initial_config+0xf/0x20 [i915] [ 11.932801] [<ffffffff810885b3>] ? async_run_entry_fn+0x33/0xe0 [ 11.932805] [<ffffffff8107fc6e>] ? process_one_work+0x1ee/0x4a0 [ 11.932809] [<ffffffff8107ff62>] ? worker_thread+0x42/0x4d0 [ 11.932812] [<ffffffff8107ff20>] ? process_one_work+0x4a0/0x4a0 [ 11.932815] [<ffffffff81085704>] ? kthread+0xd4/0xf0 [ 11.932818] [<ffffffff817c5ba4>] ? __switch_to_asm+0x34/0x70 [ 11.932821] [<ffffffff81085630>] ? kthread_park+0x50/0x50 [ 11.932824] [<ffffffff817c5c37>] ? ret_from_fork+0x57/0x70 [ 11.932827] ---[ end trace ea5a2fb99d3efe99 ]--- [ 11.934107] fbcon: inteldrmfb (fb0) is primary device [ 11.934449] ------------[ cut here ]------------Linux user
chat XMPP galen@jabber.atNovember 20, 2018 at 1:58 pm #13551Memberdelix02
November 23, 2018 at 4:16 pm #13658Member
galen
::there are some old instructions in that guide.
My kern errors do not have an Ooops.
anyways I am giving up on antiX on said machine; too many errorsLinux user
chat XMPP galen@jabber.at -
AuthorPosts
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.