Comment 168 for bug 204996

Well, I'm back again.
I haven't had a lock up for almost a day. Thats a new record. I guess the problem was having JMicron on in my BIOS, or my BIOS was too old and I updated it. I don't even have raid configured (which is what JMicron is for) so I don't get how that would cause a problem.
Well, it seems we were having multiple problems. I don't even have a wireless adapter to be the cause. So I guess if anyone can pop into their BIOS and turn off JMicron, we could see if that fixes it for some more people.
Or it could be the updated BIOS. I have an Asus m2v-mx motherboard.
I'm gonna go back into BIOS and turn JMicron back on to see if it locks up.

Hey Dylan,
That's a good idea. It should be able to work, though in my experience it locks up on both my hard drives, so it might do the same thing with network drives. And if the program (or whatever) that transfers files over the network isn't already loaded into RAM, then it probably won't work because it would need to read the drive if it isn't. I've seen what it shows in System Log during and after a lockup, but I don't really remember what it said. If u get lock ups like mine where it has a chance of coming back, (but if it needs to read the disk it crashes) you can leave system log viewer open and wait for a lock up. That's what I did. But don't expect it to save those logs the disk.

-Invader Amoto