| 1 |
Michael Orlitzky wrote: |
| 2 |
> On 07/09/11 16:56, Dale wrote: |
| 3 |
> |
| 4 |
>> No worries. Sometimes when you back up a bit, you may realize you |
| 5 |
>> missed something. I did run memtest and it bad about 45 passes I think |
| 6 |
>> with no errors. That takes a while when you have 16Gbs. o_O |
| 7 |
>> |
| 8 |
> Ah, ok. I'd also try a hard drive scan to make sure firefox's stuff |
| 9 |
> isn't sitting on bad sectors. |
| 10 |
> |
| 11 |
> Applications shouldn't be able to cause a kernel panic, period. So if it |
| 12 |
> isn't hardware, it's a kernel bug by definition. |
| 13 |
> |
| 14 |
> |
| 15 |
|
| 16 |
I'm going to try having a fresh .mozilla directory as soon as I can. |
| 17 |
I'm sort of enjoying having KDE right now. ;-) |
| 18 |
|
| 19 |
I don't think it is the hard drive. I did a fresh install on a spare |
| 20 |
drive with the same results. so, I'm beginning to think it is a kernel |
| 21 |
bug but the thing is, I have tried several versions of that too. |
| 22 |
|
| 23 |
Basically, this is plain confusing. I can't see how Firefox, or |
| 24 |
something it has to access, can cause a kernel panic. Thing is, I can't |
| 25 |
think of anything else that could be the problem but trying different |
| 26 |
versions of a kernel makes me think it is not the kernel either. |
| 27 |
|
| 28 |
< sighs > |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
Archives