[Bugme-new] [Bug 40902] New: sata_nv driver leaves BIOS in strange state on reboot

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=40902

           Summary: sata_nv driver leaves BIOS in strange state on reboot
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 2.6.38
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Serial ATA
        AssignedTo: jgarzik at pobox.com
        ReportedBy: david at davidkrider.com
        Regression: No


When rebooting from Linux, either to go into Windows or back into Linux, my
computer will get to a point in the loading process, and then spontaneously
reboot. In either OS, it's about the time to mount drives and get serious about
loading the rest of the system. If I halt, and then power the computer back up,
the BIOS will start to do it's thing, the keyboard lights will come on, the
monitor power button briefly stops flashing, and then the BIOS itself reboots.
When it finally gets back up, it tells me that the last boot failed.

This wasn't a problem for me in 2.6.36. I've downgraded and confirmed the
problem goes away. It never does this when rebooting from Windows. I'm
convinced it's not my hardware.

Twice, now, I've had to deal with a scrambled /home directory (fixed by a
fsck), which has never happened to me before in the ~15 years I've run Linux.
I'm nervous that I'm going to lose data here. I use a fakeraid to access a
stripe on which I have both Windows and Linux loaded, and I suspect the sata_nv
driver, but I have no way to catch the problem to try to diagnose if that's the
problem at all, and, if it is, where it jumps the rails.

Can anyone suggest a way to capture the problem? Maybe it's not storage at all,
but the dirty /home problems are the only thing I have to go on right now.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.