* RE: 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5
@ 2003-09-14 19:00 Pat LaVarre
0 siblings, 0 replies; 3+ messages in thread
From: Pat LaVarre @ 2003-09-14 19:00 UTC (permalink / raw)
To: mhf; +Cc: mpm, p.lavarre, linux-kernel
> If it is specific to -test5, post (as tar.bz2)
Definitely not specific to 2.6.0-test5: I have
repeatedly seen 2.6.0-test4 crash this way too.
Whether I have had this vulnerability for days or
weeks or months or years I am not yet sure, I do not
customarily make a point of trying chvt much with each
new kernel.
Unless I hear otherwise, hopefully within hours, when
next I manage to visit my console in person:
1) I will test to see if the script can crash:
2.6.0-test4 with my near default .config
2.4.22 with my near default .config
2.4.21-xfs Knoppix booted via cd
2) After the reboot following a crash of 2.6.0-test5 I
will sample:
lspci -v
/var/log/dmesg
X version and driver info from /var/log/XFree86.log
.config
3) I will report back here, attaching (2) as .tar.bz2.
Pat LaVarre
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <1063378664.5059.19.camel@patehci2>]
* Re: console lost to Ctrl+Alt+F$n in 2.6.0-test5
@ 2003-09-13 1:57 ` Matt Mackall
2003-09-13 13:38 ` Pat LaVarre
0 siblings, 1 reply; 3+ messages in thread
From: Matt Mackall @ 2003-09-13 1:57 UTC (permalink / raw)
To: Pat LaVarre; +Cc: linux-kernel
On Fri, Sep 12, 2003 at 06:49:08PM -0600, Pat LaVarre wrote:
>
> > I'm working on this, it's rather messy. Your lockup might be caused by
> > printk spew during console switch, see if it still locks up with the
> > sleep debugging turned off.
>
> Yes, thank you, Ctrl+Alt+F$n now works if only I
> CONFIG_DEBUG_SPINLOCK_SLEEP=n.
>
> Also `sudo cat /proc/kmsg | tee ...` also suddenly starts working.
>
> I wonder if somehow /proc/kmsg now working is a clue? Back with =y, my
> `dmesg` was clean but via /proc/kmsg I was seeing garbage like
>
> mmae t itbl
>
> or:
>
> mmae t itle
What video are you using? I'm guessing you've got a framebuffer console?
VESA by any chance?
> for what now again is such reassuring chatter as:
>
> <6>scsi2 : SCSI emulation for USB Mass Storage devices
> <5> Vendor: Iomega Model: RRD Rev: 23.D
> <5> Type: CD-ROM ANSI SCSI revision: 02
> <7>WARNING: USB Mass Storage data integrity not assured
> <7>USB Mass Storage device found at 3
> <4>sr1: scsi3-mmc drive: 125x/125x caddy
> <4>sr1: scsi3-mmc maybe not writeable
> <4>sr1: scsi3-mmc writable profile: 0x0002
> <7>Attached scsi CD-ROM sr1 at scsi2, channel 0, id 0, lun 0
>
> Pat LaVarre
>
> P.S. I could easily check to see if =y kills an ssh session or just the
> display, if that helps.
That might help track down a bug in the console, sure. Not sure what's
going on with /proc/kmsg though.
> P.P.S.
>
> Tentatively I conclude "sleep debugging ... off" meant this .config
> change because I see:
Yep, that's the one.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: console lost to Ctrl+Alt+F$n in 2.6.0-test5
2003-09-13 1:57 ` Matt Mackall
@ 2003-09-13 13:38 ` Pat LaVarre
2003-09-14 0:24 ` 2.6.0-test5: intermittent crash on chvt to X; was " Michael Frank
0 siblings, 1 reply; 3+ messages in thread
From: Pat LaVarre @ 2003-09-13 13:38 UTC (permalink / raw)
To: mpm; +Cc: linux-kernel
> What video are you using?
> I'm guessing you've got a framebuffer console?
> VESA by any chance?
I do not yet know how to answer such questions confidently.
I see (redhat-config-xfree86 --> tab Advanced) reports:
Video Card
Video Card Type = Intel 865
Memory Size = 16 megabytes
Driver = i810
Enable Hardware 3D Acceleration = no
> > Yes, thank you, Ctrl+Alt+F$n now works
> > if only I CONFIG_DEBUG_SPINLOCK_SLEEP=n.
Please allow me to disavow that first impression.
With CONFIG_DEBUG_SPINLOCK_SLEEP=y, I've now been counting keystrokes
til crash. I count each of Ctrl+Alt+F5 and Ctrl+Alt+F7 as one stroke.
Sometimes I crash, sometimes I do not. I began logging life more
carefully when first I saw a few strokes cause a crash, and thereafter,
per boot:
8 strokes crashed.
60 strokes did not crash, so I gave up and rebooted to try again.
4 strokes crashed. The first 2 seeming had logged me out, killing my
cat /proc/kmsg process.
8 strokes crashed.
26 strokes crashed.
...
The only consistency I see is that always an even number of strokes
cause a crash i.e. always the Ctrl+Alt+F7 switch back to my X console,
not the switch to a text console.
To prepare to crash, I only know of: sync umount ext3. For me as yet
"Checking ... filesystem..." wastes less than three minutes per crash,
and I haven't yet perceptibly lost a disk.
> > I wonder if somehow /proc/kmsg now working is a clue?
Meanwhile, whether `sudo cat /proc/kmsg | tee ...` displays printk
intact or not also varies, without clearly correlating with whether a
crash will or will not occur.
So far, with CONFIG_DEBUG_SPINLOCK_SLEEP=y, trying `sudo cat /proc/kmsg
| tee ...` has never run well enough to capture the cause of the crash.
> > I could easily check ... ssh ...
Remote ssh freezes and remote ping starts losing all packets.
Pat LaVarre
^ permalink raw reply [flat|nested] 3+ messages in thread
* 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5
2003-09-13 13:38 ` Pat LaVarre
@ 2003-09-14 0:24 ` Michael Frank
2003-09-14 23:04 ` Pat LaVarre
0 siblings, 1 reply; 3+ messages in thread
From: Michael Frank @ 2003-09-14 0:24 UTC (permalink / raw)
To: Pat LaVarre, mpm; +Cc: linux-kernel
> I ended by running the third variant script quoted below. Now my logs
> comfortingly end with 'switching to X'. I presume I'm catching the
> crash in the last sleep $wait.
Makes sense because the crash may (in your case does) happen later
in the switching sequence at which time the "new" log already made
it to disk - I'll use your variant from now on ;)
The qestion now is whether this is kernel or X related.
Have you had this problem with an earlier 2.6 or 2.4 kernel?
If it is specific to -test5, post (as tar.bz2)
- lspci -v
- /var/log/dmesg
- X version and driver info from /var/log/XFree86.log
- .config
Regards
Michael
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5
2003-09-14 0:24 ` 2.6.0-test5: intermittent crash on chvt to X; was " Michael Frank
@ 2003-09-14 23:04 ` Pat LaVarre
0 siblings, 0 replies; 3+ messages in thread
From: Pat LaVarre @ 2003-09-14 23:04 UTC (permalink / raw)
To: mhf; +Cc: mpm, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
> qestion now is whether this is kernel or X related.
Oh.
> > echo ... | tee -a $log
> > sync
> > sleep $wait
> > chvt ...
> > sleep $wait
>
> the crash may (in your case does) happen later
In repeating those five commands, is there any purpose to the first
sleep? I left the first sleep in place to match the original, but once
I assume sync leaves no writes unflushed then now I do not see what the
first sleep accomplishes, if anything.
> Have you had this problem with an earlier 2.6 or 2.4 kernel?
Today 2.4.21-xfs Knoppix booted via cd:
in over 75 cycles I saw no crash so I gave up.
Today 2.4.22 with a near default .config:
"in over 75 cycles I saw no crash so I gave up".
Today 2.6.0-test4 with a near default .config:
Counting cycles before crash per boot I saw: 3 2 16 ...
Yester/today 2.6.0-test5 with a near default .config:
"I saw: 1 18 20 20 ... 4 16 ..." 3 ...
> -test5, post (as tar.bz2) ...
After that last -test5 crash I rebooted and then produced the attached
via:
#!/bin/bash
# rm -r chvtx
mkdir chvtx
sudo /sbin/lspci -v >>chvtx/v.lspci
sudo cat /var/log/dmesg >>chvtx/var.log.dmesg
egrep -i 'version|release|driver' /var/log/XFree86.*.log >>chvtx/var.log.XFree86.log
# cp -ip /var/log/XFree86.*.log chvtx/
cp -ip .config chvtx/config
tar -c chvtx | bzip2 -zc >chvtx.2.6.0-test5.tar.bz2
# Pat LaVarre
[-- Attachment #2: chvtx.2.6.0-test5.tar.bz2 --]
[-- Type: application/x-bzip, Size: 12515 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-09-14 23:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-14 19:00 2.6.0-test5: intermittent crash on chvt to X; was console lost to Ctrl+Alt+F$n in 2.6.0-test5 Pat LaVarre
[not found] <1063378664.5059.19.camel@patehci2>
2003-09-13 1:57 ` Matt Mackall
2003-09-13 13:38 ` Pat LaVarre
2003-09-14 0:24 ` 2.6.0-test5: intermittent crash on chvt to X; was " Michael Frank
2003-09-14 23:04 ` Pat LaVarre
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®