kernel panic with dm-crypt/luks + lvm + xfs + ubuntu kernel

[Dustin Widmann]

Binary package hint: linux-source-2.6.20

I really should have done this a while ago. This was with the 2.6.20-15 kernel IIRC, but I think I had troubles with 2.6.17-* also.

I had decided to play with dmcrypt with my debian etch install, two weeks later I decided it was time to move back to ubuntu, and my home partition was still in encrypted lvm.

Details:

- using lvm2 (so I can have one partition span two drives, a seagate SATA 250gb and a seagate SATA 400gb)
- using AES 256-bit to encrypt a ~600gb XFS partition, with LUKS.
- I set LUKS and friends up on Ubuntu following a guide I found in the ubuntu wiki, and it seems to get in just fine.
- After I get in (ie, usually after startup), when using the 2.6.20-15-generic ubuntu kernel, quite randomly, after a bit of IO on the encrypted partition, I start getting kernel messages leading to an eventual total lockup.
- For now I'm using 2.6.18, and it otherwise works fine ... just not with my setup apparently :(

I'm aware that 2.6.20-16 is out now, and I'll be trying it momentarily. I'll also be sure to grab some exact error messages and post back.

[Dustin Widmann (blackwaltz)]

Okay, I've now tried it with 2.6.20-16, same deal.
It usually starts messing up after being used for a while, but heavy IO speeds up the process. After it starts, it's impossible to reboot. I have to the power button.
I've attached the syslog (it's the 2.6.20-15 one, but the errors it threw at me looked the same)
I'll just attatch the whole file and let you (whoever you is) decide what's relevant.

[Dustin Widmann (blackwaltz)]

Oh, a couple more details:

It's the x86_64 kernel.
My motherboard is an ASUS A8N SLI Premium
when I say heavy IO, well, this will do the trick: "cp kubuntu_7.04_amd64.iso blah.iso"

[Dustin Widmann (blackwaltz)]

Seems the LVM part is irrelevant, I have the same problem when not using LVM too.

Problem is still present in 7.10.

[Dustin Widmann (blackwaltz)]

Seems it's not just with dm_crypt either - The same problem also occurs when using truecrypt (which I believe also loads dm_mod?)

[Dustin Widmann (blackwaltz)]

Seems like this bug is probably related to https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/156669

If this is the case, then mayhap the problem is linked to nforce4 + sata_nv. This would also seem to make the filesystem type negligible.

[Leann Ogasawara (leannogasawara)]

Hi Dustin,

I posted a similar comment in the bug 156669. The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel bug against 2.6.22 this will be closed. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!