Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30974 - [linux] 3.5.0 Kernel Panic when mounting partition using AOE

Attached to Project: Arch Linux
Opened by Curtis (foxcm2000) - Thursday, 02 August 2012, 11:42 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 01 September 2012, 05:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading to kernel 3.5, the kernel panics whenever I attempt to mount a partition using ATA over Ethernet (AOE).
The aoe module loads OK and the aoe-discover and aoe-stat utilities correctly identify the drive, but the kernel panics when the mount command is executed.

Additional info:
* package version(s)
Kernel: 3.5
Aoetools: 30
Vblade (running on server, not on client machine that is panicking): 20


* config and/or log files etc.


Steps to reproduce:
1. Boot using Linux kernel 3.5 from Arch testing.
2. modprobe aoe
3. mount a partition over aoe and the kernel panics.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 01 September 2012, 05:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.5.3-1
Comment by Curtis (foxcm2000) - Friday, 03 August 2012, 00:28 GMT
Update: The kernel panic only happens when there are multiple AOE targets. For example, I was using 2 Gig-E adapters to communicate with the server, but when I killed one of the vblade instances on the server, the mount proceeded without crashing.

The bug still exists, but is now limited to using multiple AOE targets in parallel. I have been using this configuration for over 2 years and many kernel releases, so this is a regression.
Comment by Jan de Groot (JGC) - Friday, 03 August 2012, 12:11 GMT
Without giving more information about the traces in the kernel panic, nobody will fix this for you.
Comment by Tobias Powalowski (tpowa) - Wednesday, 08 August 2012, 06:49 GMT
We can't fix here anything please report upstream.
Comment by Curtis (foxcm2000) - Wednesday, 08 August 2012, 23:36 GMT
I'll report upstream. Sorry for the lack of traces but kernel panics are not the easiest things to log.
Comment by Swift Geek (swiftgeek) - Tuesday, 21 August 2012, 00:06 GMT
They are easy with nullmodem
Comment by Curtis (foxcm2000) - Saturday, 01 September 2012, 02:39 GMT
You can go ahead and close this bug. The latest kernel packages (linux 3.5.3-1) have fixed the problem.

Loading...