Willie Wong wrote:
On Sat, Jul 23, 2011 at 09:45:07AM -0500, Dale wrote:
YoYo Siska wrote:
I guess it starts to download it to a temp file, than moves it to the
file you choose (never looked into it)... so the problem would be most
likely in that operation..
I just find it downright odd that a browser causes a panic because
of a download when other programs, like emerge, can download just
fine.
Dale, what YoYo meant was precisely that: emerge gets files using wget
(unless you configured it otherwise) which writes directly to the
directory, whereas Firefox would first download something to (I guess)
/tmp and (according to YoYo) write it to the "correct" name/directory
once you give it to the browser. So YoYo is suspecting that it is this
move of the file from /tmp (or whereever) to your download directory
that is giving the kernel panic.
BTW, you mentioned that this happened after a power-outage. Have you
completely checked your disks and filesystem's health?
W
I understand what he was saying and I already knew it done it that way.
I posted that in a reply somewhere. It does the initial part to /tmp
until you tell it otherwise, then it goes there. I can't recall it not
being that way. It's just hard for me to believe that Firefox or
Seamonkey downloading some file would cause a kernel panic like this.
This just isn't like Linux.
I think the power outage was a coincidence at this point. That said, I
have tested all sorts of things including running memtest. Hardware
wise, everything seems fine. I also blew out the dust bunnies which was
not much. I generally do this about every month or so.
Just hoping some update will change things, eventually.
Dale
:-) :-)
