1 |
Mark Knecht wrote: |
2 |
> On Sat, Jul 9, 2011 at 4:55 PM, Dale<rdalek1967@×××××.com> wrote: |
3 |
> |
4 |
>> Mark Knecht wrote: |
5 |
>> |
6 |
>>> And this is exactly why you should consider posting any information |
7 |
>>> your can find on LKML to let the heavy weight guys figure it out. As I |
8 |
>>> said earlier, I believe they will take you quite seriously. In general |
9 |
>>> I would also say that Firefox should be able to cause a kernel panic, |
10 |
>>> and since it is I know the kernel developers are going to be |
11 |
>>> interested in what's the root cause. |
12 |
>>> |
13 |
>>> I don't remember from earlier why you said it was a kernel panic, but |
14 |
>>> clearly it must be. How are you determining this? Do you have info in |
15 |
>>> a terminal? For a few problems I've had I've posted digital photos |
16 |
>>> I've taken and uploaded to FlickR. You might consider doing something |
17 |
>>> similar. |
18 |
>>> |
19 |
>>> Cheers, |
20 |
>>> Mark |
21 |
>>> |
22 |
>>> |
23 |
>>> |
24 |
>>> |
25 |
>> The reason I said kernel panic is because someone else posted that when the |
26 |
>> keyboard lights blink, that is a kernel panic. Sure enough, when Neil told |
27 |
>> me how to set it up so that it would automatically reboot when the kernel |
28 |
>> panics, it does just that. I have no reason to think it is anything other |
29 |
>> than a kernel panic based on nothing but the kernel doing the reboot and the |
30 |
>> lights blinking. |
31 |
>> |
32 |
>> I would like to report this but I wouldn't even know where to start. If I |
33 |
>> had a lot more knowledge on how to help track it down, then that would be |
34 |
>> different. I'm not sure I can help much other than telling them Firefox |
35 |
>> causes a kernel panic but I have no clue how or why. |
36 |
>> |
37 |
>> Then again, if one of the dev would hold my hand a little, I could copy a |
38 |
>> install over to my spare drive and then not have to worry about messing up |
39 |
>> my main install. Fluxbox is OK but I like my KDE better. ;-) |
40 |
>> |
41 |
>> My old rig was in the middle of a update and we just had a nasty little |
42 |
>> thunderstorm here. It was OOo of course. It was 7 hours into a 9 hour |
43 |
>> compile when the lights blinked. My old rig isn't on a UPS anymore. Neat |
44 |
>> huh? I'm glad for the rain tho. My garden needs it really really bad. |
45 |
>> |
46 |
>> Dale |
47 |
>> |
48 |
> Yeah, if you can't report good clear info then it's just a waste of |
49 |
> everyone's time. No need to do that. |
50 |
> |
51 |
> Not sure if it would work or even apply but there are some kernel |
52 |
> features, mostly I think used around boot time, that send kernel info |
53 |
> over either a serial port or more recently an Ethernet link to another |
54 |
> computer which then stays alove and captures whatever data gets |
55 |
> transmitted. If you were interested in learning about that (I am but |
56 |
> haven't had time. I used it years ago to give some LKML guys info they |
57 |
> needed to get an ATI chipset to work better) then we might be able to |
58 |
> dig into that off line. |
59 |
> |
60 |
> On the other hand, if you're machine is working then it ain't broke, right? ;-) |
61 |
> |
62 |
> Cheers, |
63 |
> Mark |
64 |
> |
65 |
> |
66 |
> |
67 |
|
68 |
It works as long as I don't open Firefox. If I open Firefox, poof!! No |
69 |
more trapped smoke. lol |
70 |
|
71 |
Dale |
72 |
|
73 |
:-) :-) |