Problem with fakeraid (sata_nv?) driver

Bug #829413 reported by Dunkirk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have an Asus Striker II Formula motherboard, which has an nVidia-based "fakeraid" SATA controller. I have 2 hard drives striped with it's firmware. Across this stripe, I have both Windows 7 and Ubuntu 11.04 installed.

Whenever I reboot from Ubuntu 11.04, the computer has to reboot twice, whether I reboot back into Windows OR Ubuntu. Either OS will get to the point of loading the primary video resolution, then spontaneously reboot the computer AGAIN. If I shutdown from 11.04, and then physically restart the computer, the BIOS will come up to the point that the lights come on the keyboard, then it will spontaneous reboot again, from within the BIOS.

Four times, now, my /home partition has gotten scrambled during the reboots, and needed an fsck. (Which was an enormous pain due to my encrypted home directory because dm_crypt doesn't like to let it go.) I was hoping that this was some sort of interaction with ecryptfs, but I took that off my home directory, and the problem happened again anyway.

This does NOT happen when rebooting from Windows. This also does NOT happen when rebooting from Ubuntu 10.10. (I downgraded for a time, and the problem went away.) It would therefore seem to be a problem with 2.6.38 which is not present with 2.6.36.

I've tried loading vanilla kernels from the PPA. That repo's 2.6.36 wouldn't boot at all. It's 2.6.37 doesn't cause the double-reboot, but it still scrambled my home directory (and that's when I removed the ecryptfs).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dkrider 2467 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdffc000 irq 46'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,10280214,00100400'
   Controls : 21
   Simple ctrls : 14
Date: Fri Aug 19 08:36:50 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=416cc9d6-0397-464d-a188-e24fa536d573
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Dell Inc. Precision WorkStation T3400
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=1d04b144-1490-407d-b564-f61db632cbef ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-10-generic N/A
 linux-backports-modules-2.6.38-10-generic N/A
 linux-firmware 1.52
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-07-26 (23 days ago)
dmi.bios.date: 03/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TP412
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/21/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3400
dmi.sys.vendor: Dell Inc.

Revision history for this message
Dunkirk (david-davidkrider) wrote :
Revision history for this message
Dunkirk (david-davidkrider) wrote :

Note that `ubuntu-bug' captured the information from my computer at work, and NOT from my home computer, where I'm having the problem. Unfortunately, I'm leaving my home computer OFF while I figure out what to do next, and there doesn't seem to be a way to submit a bug to Launchpad outside of `ubuntu-bug' any more, so... I'm sorry.

Revision history for this message
Dunkirk (david-davidkrider) wrote :

Still there as of 3.0.x...

affects: linux-lts-backport-natty (Ubuntu) → linux (Ubuntu)
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Dunkirk (david-davidkrider) wrote :

Since making this report, I had verified the existence of the bug by downloading various tar'd kernel sources and doing `fakeroot make-kpkg --initrd kernel_image kernel_headers'. I did all the versions from 2.6.36.4 through 2.6.38. I know 36.4 is good, and .38 is bad, but I got a little turned around in the .37 versions, so I'm not exactly sure where the problem came in. To address this, I downloaded the git sources. My plan was to do some git bisect'ing to find the exact patch that produces the problem. However, make-kpkg is choking on the git sources, and my first attempt at a simple `make install' produces a kernel that locks up during boot. Have you actually tracked down this bug? If so, that would save me a LOT of effort. If you need any help proving a fix, I'd be glad to give it a try.

Revision history for this message
penalvch (penalvch) wrote :

Dunkirk, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bios-outdated-a14 needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dunkirk (david-davidkrider) wrote :

I don't have this computer any more, so I can't test this. I gave up on it as there seemed to be no workaround on quick fix. (I traded it with my kids' computer so I wouldn't be bothered by the bug, then gave it away when I get a new computer.)

Revision history for this message
penalvch (penalvch) wrote :

Dunkirk, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/829413/comments/6 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.