2.6.35 panic [SOLVED]

Mitridas · n00b Joined: 12 Nov 2008 Posts: 11

Hello,
I've just compiled and installed the new 2.6.35-gentoo kernel but I can't boot it because it always fails at VFS (unable to mount root device).
My root partition is a normal ext4 and it still works with the 2.6.34-r2 kernel (I recycled the same configuration with the 2.6.35 via make oldconfig).
Any ideas??

d2_racing · Posted: Fri Aug 06, 2010 4:56 pm Post subject:

Hi, can you post this from the kernel that you are able to boot :

xibo · Posted: Fri Aug 06, 2010 5:06 pm Post subject:

can you see the disk partitions? normaly the kernel will print out a list of partitions when not able to mount it's root, it should be printed right before the kernel panic message

Mitridas · n00b Joined: 12 Nov 2008 Posts: 11

Sadly it doesn't print out any partition.
The output of the command is the following:

idella4 · Posted: Fri Aug 06, 2010 8:48 pm Post subject:

Mitridas

I'll wager this is it. I had the same thing happen with ext4.

Mitridas · n00b Joined: 12 Nov 2008 Posts: 11

Uhm I can't find the LBDAF option: under the block layer options I have only
- Block layer SG support V4
- Block layer data integrity support
- IO shedulers

and if I directly search for LBDAF via grep it doesn't find anything.

x22 · Apprentice Joined: 24 Apr 2006 Posts: 208

LBDAF option is only for 32bit architecture. 64bit kernels have it always enabled.

Mitridas · n00b Joined: 12 Nov 2008 Posts: 11

Yes infact I'm on 64 bit here.
So the problem is still open.

Hu · Administrator Joined: 06 Mar 2007 Posts: 23193

Please post the contents of the screen as of when it panics. There may be information higher up on the screen that would be useful in troubleshooting.

runem · n00b Joined: 08 Sep 2006 Posts: 40

This looks like a panic-problem I had with 2.6.35 . The options for harddisk-drivers have been shifted around so 'make oldconfig' silently deselects the drivers.
You probably have to activate:

ATA SFF support
ATA BMDMA support
<driver for your chipset>

Remember to make the driver a built-in part of the kernel

Mitridas · n00b Joined: 12 Nov 2008 Posts: 11

Oooh yes that did the trick.
It seems that in 2.6.35 the sata drivers options were relocated and infact my chipset driver
got unselected.
Thank you runem!!

d2_racing · Posted: Sat Aug 07, 2010 9:05 pm Post subject:

Nice then, I'm gonna check my .config before rebooter my box too

agent_jdh · Veteran Joined: 08 Aug 2002 Posts: 1783 Location: Scotland

I'm having what appears to be the same problem here with 2.6.35, despite correctly setting the ATA_BMDMA option for my Sil3112. Something is not right here...
_________________
Jingle Jangle Jewellery

d2_racing · Posted: Sun Aug 08, 2010 2:03 pm Post subject:

Yeah, they changed one of two options but because of that, 90% of the SATA config is not enabled.

agent_jdh · Veteran Joined: 08 Aug 2002 Posts: 1783 Location: Scotland

loopx · Posted: Sun Aug 15, 2010 6:55 pm Post subject:

lotan_rm · n00b Joined: 21 Aug 2010 Posts: 3

I have a Sil3112A chipset and

ATA SFF support
ATA BMDMA support
SATA_SIL

all enabled.

Like agent_jdh, I still get the kernel panic.

For the time being, I'll revert back to 2.6.34.

Shining Arcanine · Veteran Joined: 24 Sep 2009 Posts: 1110

swanson · Posted: Mon Aug 23, 2010 3:09 pm Post subject:

For those using sata_sil, it has been reported as kernel bug 16606 in Linux 2.6.35 not detecting the first SATA hard drive for some weird reason. Currently under investigation.
_________________
Alan.

lotan_rm · n00b Joined: 21 Aug 2010 Posts: 3

@Shining Arcanine: Yes, 2.6.34 is using the same driver.

@swanson: Thanks for the hint. Sounds very similar to my issue.

depontius · Advocate Joined: 05 May 2004 Posts: 3530

I'm now into the same problem, except I'm unable to mount my root drive on PATA.

This system crashed last weekend, and I'm rebuilding now, adding a new 1TB drive, removing a bad 160GB drive, and keeping a good 200GB drive. The system used to boot off of the 160GB drive, and it's currently booting a temporary FC12 install on the 1TB drive. I'm trying to install Gentoo on the 200GB drive. I'm planning to keep the 1TB temporarily as storage for MythTV, but later this fall I plan to migrate my mythbackend to a new computer, and the 1TB drive along with it. This way, this system will see minimal disruption, with the OS installed on the 200GB drive.

Right now I'm booting off of the MBR and grub.conf from the FC12 install, and I've added an entry for the new Gentoo install, pointing it correctly to /boot on the 200GB drive. The new kernel boots, loads the initrd, and dies as it's trying to mount my real root partition. I remember having a problem like this on a different machine, needing to set some sort of "large drive" option in order to use an ext4 root, but a quick search here indicates that that option is only needed for 32-bit, and 64-bit (which this machine is) has that built-in.

Nor is it a matter of drivers. All of my disks are present. When mounting root fails, I can drop to a shell and "ls /dev/sd*" and my drives are all (I haven't actually removed the 160GB drive, yet.) there. I checked and I have EXT4 enabled

........ Found it - I think. I'm going to post this anyway, in case anyone else ever stumbles across this.

I have "CONFIG_EXT4_FS=m"

Clearly it needs to be "y". By way of explanation, the previous installation predated ext4. I had ext4=m so I could play around with it, and since my root was ext3 that was OK. When checking menuconfig, I merely noticed that -something- was there, without looking too closely. I found the problem with grep.

Off to recompile.
_________________
.sigs waste space and bandwidth

monsm · Guru Joined: 26 Sep 2007 Posts: 467 Location: London, UK

swanson · Posted: Thu Sep 09, 2010 10:04 am Post subject:

And apparently reverting the patch libata: Remove excess delay in the tf_load path fixes the sata_sil issue.
_________________
Alan.

slackline · Posted: Thu Sep 09, 2010 11:34 am Post subject:

Been scratching my head over this issue past few days and grep-ing my .config from 2.6.34 and comparing to 2.6.35 looking for what differs, will be trying these out later.
_________________
"Science is what we understand well enough to explain to a computer. Art is everything else we do." - Donald Knuth

slackline · Posted: Thu Sep 09, 2010 6:37 pm Post subject:

Sorted, I'd enabled one ATA BMDMA driver support but actually have two controllers.

An easy way to check what drivers you need is to boot into a working console and do the following, the output tells you what drivers are in use...