Todd Goodman wrote:
It's certainly possible it's unrelated. Or it could be something similar and the other bug reporter made a mistake bisecting or didn't run long enough to fail with that bisection. It's possibly a lot of things since we don't have enough information. I don't think that would work OK (but don't know for sure.) In most cases it would probably work OK as I believe unused parameters will be ignored. But if a parameter was removed or the meaning changed then you might have a problem (unlikely I'd guess, but I don't know.) Todd
Here is a update. Let's see what folks think about this situation. I mentioned in another thread that I did a from scratch kernel. It was a .35 version. It seemed to work fine, for a while. When I tell Seamonkey to download to my desktop, it works fine. The minute I tell it to save it to my large 750Gb drive, I get a kernel panic. Keep in mind, there is nothing OS related on that drive. Nothing OS at all. It is videos, CD ISO's and such as that.
Here is another thing I just found out. I did download a few videos I wanted to save. They were on my desktop and who likes desktop clutter. So, I dragged them over to the large data drive. I did this by dragging from the desktop to a open Konqueror window. This was not downloading or anything, just a straight move operation. It copied a few Mbs and panic. This had nothing to do with Seamonkey either.
So, did this issue just move from a Seamonkey sort of problem to completely something else? Hmmmmm. After the crash, I boot to single user mode. I ran resierfsck --fix-fixable on the drive. Not one error. I ran the smart thingy and not one error there either. Thinking file system is bad in the kernel, well my /home directory is on reiserfs too. It is the one that works.
Now, what the heck is this about? Does this make sense to anyone? Dale :-) :-)
