Opened 6 years ago
Last modified 4 years ago
#13911 closed bug
hrev51714-x86_gcc2_hybrid_anyboot kernel issue due to mild terminal usage and webpositive — at Version 4
Reported by: | domcaf | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | File Systems/packagefs | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
hrev51714-x86_gcc2_hybrid_anyboot kernel issue due to mild terminal usage and webpositive
REPRODUCTION STEPS:
- Run from USB thumbdrive on physical hardware.
- Make it to desktop.
- Enter WiFi/WPA credentials.
- Open terminal and issue following commands:
ping -c2 www.yahoo.com
for which successful responses received.set -o vi
.ping -c2 www.google.com
for which successful responses received.- {{{perl -v" which produces expected output.
- Closed terminal by typing using ctrl-d key sequence.
- Opened webpositive with no success.
- Open terminal again with no success.
- Kernal debugger starts up by itself. See attached photos of white background debugger output and "bt" command output. Multiple photos of each provided in case one photo is easier to view than another.
- Was able to get same behavior multiple times using above steps. Additional hardware info also attached in case this is processor/hardware specific.
- Thanks for reviewing!
Change History (16)
by , 6 years ago
Attachment: | IMG_20171228_153212.jpg added |
---|
by , 6 years ago
Attachment: | IMG_20171228_153234.jpg added |
---|
Initial debugger output after it started automatically, background is white, alternate photo in case more readable
by , 6 years ago
Attachment: | bt-IMG_20171228_183315.jpg added |
---|
kernel "bt" command output; alternate for readability alternative
by , 6 years ago
Attachment: | TestBed-system-info_20171227.txt added |
---|
Hardware info on which problem occurred using "sysinfo" utility when same system booted into Lubuntu Linux
comment:1 by , 6 years ago
Keywords: | kernel debugger self start removed |
---|---|
Priority: | high → normal |
Can you please get the file /var/log/syslog
from the booted Haiku system (before you reproduce the crash, of course) and upload it here? (Or is that somehow not possible?)
Secondly, have you run a memtest86+
on this system recently?
comment:2 by , 6 years ago
memtest86+ ran thru 3 full cycles with no errors before I stopped testing. Please see attached screenshots. Will try to get you syslog soon.
by , 6 years ago
Attachment: | memtest86plus-IMG_20171229_003013.jpg added |
---|
memtest86+ results screenshot
comment:3 by , 6 years ago
patch: | 0 → 1 |
---|
by , 6 years ago
Attachment: | memtest86plus-IMG_20171229_003025.jpg added |
---|
memtest86+ results screenshot alternate for readability
comment:4 by , 6 years ago
Component: | - General → File Systems/packagefs |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
Platform: | x86 → All |
Initial debugger output after it started automatically, background is white.