The kernel should really say what the
[ cut here ]
lines are called, else users will say things like:
"I discovered that the user needs to use xrandr in _two_ steps for
certain resolutions, else he will trigger a
kernel: [ cut here ] line."
The kernel should really say what the
[ cut here ]
lines are called, else users will say things like:
"I discovered that the user needs to use xrandr in _two_ steps for
certain resolutions, else he will trigger a
kernel: [ cut here ] line."
Most users won't even know what string from this to google on to find
out what this is all about:
Jul 03 13:57:20 jidanni7 kernel: [ cut here ]
Jul 03 13:57:20 jidanni7 kernel: recvmsg bug 2: copied 73BCB6CD seq 70F17CBE
rcvnxt 73BCB9AA fl 0
Jul 03 13:57:20 jidanni7
Most users won't even know what string from this to google on to find
out what this is all about:
Jul 03 13:57:20 jidanni7 kernel: [ cut here ]
Jul 03 13:57:20 jidanni7 kernel: recvmsg bug 2: copied 73BCB6CD seq 70F17CBE
rcvnxt 73BCB9AA fl 0
Jul 03 13:57:20 jidanni7
http://stackoverflow.com/questions/4864875/folder-for-temporary-files-creation-in-android-why-does-data-local-tmp-doesnt
says
"Directories in Linux are accessible even if you don't have permissions
to open their parent directory."
Could someone with enough Stackoverflow reputation points to
http://stackoverflow.com/questions/4864875/folder-for-temporary-files-creation-in-android-why-does-data-local-tmp-doesnt
says
Directories in Linux are accessible even if you don't have permissions
to open their parent directory.
Could someone with enough Stackoverflow reputation points to enable
Problem: boot messages fly off the screen before the kernel panic is reached.
Possible to write boot messages to a file on a USB stick?
Gentlemen, we all know what a hassle it can be to get all those error
messages that fly off your screen upon failed boots. One needs extra
equipment etc.
Well
Problem: boot messages fly off the screen before the kernel panic is reached.
Possible to write boot messages to a file on a USB stick?
Gentlemen, we all know what a hassle it can be to get all those error
messages that fly off your screen upon failed boots. One needs extra
equipment etc.
Well
Here's another one I saw occupying the screen:
[...] ---[ end trace ... ]---
[...] Fixing recursive fault but reboot is needed!
Make sure that the user can also turn that one off and run it again to
reveal the messages that were pushed off the screen above it.
--
To unsubscribe from this list:
Here's another one I saw occupying the screen:
[...] ---[ end trace ... ]---
[...] Fixing recursive fault but reboot is needed!
Make sure that the user can also turn that one off and run it again to
reveal the messages that were pushed off the screen above it.
--
To unsubscribe from this list:
> "RD" == Randy Dunlap writes:
RD> When would you want to disable it? at kernel boot time (as a boot option)
RD> or sometime later?
RD> But would you only want to disable Call Trace: on panics or any time that a
RD> call trace might be printed? and would disabling call trace also disable
RD == Randy Dunlap rdun...@infradead.org writes:
RD When would you want to disable it? at kernel boot time (as a boot option)
RD or sometime later?
RD But would you only want to disable Call Trace: on panics or any time that a
RD call trace might be printed? and would disabling call trace
Idea: if the user could disable
the "Call Trace:"
seen upon "Kernel panic - not syncing: attempted to kill init!"
he would then be able to see more lines above without having it shoved
off the screen with the useless (to him) call trace.
e.g., using panic=222 call_trace=disabled would give him
Idea: if the user could disable
the Call Trace:
seen upon Kernel panic - not syncing: attempted to kill init!
he would then be able to see more lines above without having it shoved
off the screen with the useless (to him) call trace.
e.g., using panic=222 call_trace=disabled would give him enough
>> kernel-parameters.txt says what ACPI and APM stand for, but not APIC.
J> Advanced PIC, most likely.
Also say what PIC means.
J> http://en.wikipedia.org/wiki/APIC will tell more.
Not when one is having booting problems and can't connect their modem.
>> Also there give some basic apm related
kernel-parameters.txt says what ACPI and APM stand for, but not APIC.
J Advanced PIC, most likely.
Also say what PIC means.
J http://en.wikipedia.org/wiki/APIC will tell more.
Not when one is having booting problems and can't connect their modem.
Also there give some basic apm related
Fellows, please note http://bugs.debian.org/322487 . I am not the
right person to write content, as I wouldn't know what to write, as I
am not a computer pro. Never tampered with kernels, etc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Fellows, please note http://bugs.debian.org/322487 . I am not the
right person to write content, as I wouldn't know what to write, as I
am not a computer pro. Never tampered with kernels, etc.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
18 matches
Mail list logo
