Fatal kernel panic (nvidia?)

Llama · 2012-06-23 10:52:07

Hi,

After an upgrade about ten days ago, I've got fully dysfunctional system, i.e. both images, current and fallback, panic.

Such bugs usually don't last long; I suppose a regular chroot/upgrade would suffice.

Taking archbang for a livecd I immediatly run into trouble:

[live@archbang ~]$ fdisk -l
[live@archbang ~]$

Meanwhile, the HD partitions are visible. Any ideas?

Last edited by Llama (2012-07-09 13:54:13)

Trilby · 2012-06-23 13:33:10

Ah ... I don't think that should give anything when run as a normal user. I have to be root (or sudo) here for fdisk -l to list anything.

Llama · 2012-06-23 19:06:04

Trilby wrote:

Ah ... I don't think that should give anything when run as a normal user. I have to be root (or sudo) here for fdisk -l to list anything.

Right you are. Thanks!

[live@archbang ~]$ sudo fdisk -l
Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ef9d3
Device Boot Start End Blocks Id System
/dev/sda1 63 2040254 1020096 82 Linux swap / Solaris
/dev/sda2 2040255 67569389 32764567+ 83 Linux
/dev/sda3 67569390 2930272064 1431351337+ 83 Linux
Disk /dev/mapper/arch_root-image: 3831 MB, 3831496704 bytes
255 heads, 63 sectors/track, 465 cylinders, total 7483392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sdb: 988 MB, 988282880 bytes
32 heads, 63 sectors/track, 957 cylinders, total 1930240 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 135 1929311 964588+ 6 FAT16
[live@archbang ~]$

Llama · 2012-06-23 19:57:32

To whom it may concern:

[live@archbang ~]$ sudo mkdir /mnt/arch
[live@archbang ~]$ sudo mount /dev/sda2 /mnt/arch
[live@archbang ~]$ cd /mnt/arch/
[live@archbang arch]$ sudo mount -t proc proc proc/
[live@archbang arch]$ sudo mount -t sysfs sys sys/
[live@archbang arch]$ sudo mount -o bind /dev dev/
[live@archbang arch]$ sudo mount -t devpts pts dev/pts
[live@archbang arch]$ sudo chroot . /bin/bash
[root@archbang /]# pacman -Sy
:: Synchronizing package databases...
core 104.3 KiB 434K/s 00:00 [######################] 100%
haskell 34.9 KiB 87.7K/s 00:00 [######################] 100%
extra 1404.7 KiB 888K/s 00:02 [######################] 100%
community 1700.1 KiB 797K/s 00:02 [######################] 100%
archlinuxfr 34.5 KiB 271K/s 00:00 [######################] 100%
[root@archbang /]# pacman -Su
:: Starting full system upgrade...

Llama · 2012-06-23 20:51:02

Unfortunately, the kernel panic is still there. It's called panic for a reason: no way to pinpoint the real source of trouble. It looks like the system decided finally to die on me.

Llama · 2012-06-24 07:31:37

Checked the partitions (because of the suggestive panic messages):

[root@archbang /]# sudo fsck /dev/sda3
fsck from util-linux 2.21.2
e2fsck 1.42.4 (12-June-2012)
HomeS contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
HomeS: 463505/89464832 files (10.6% non-contiguous), 309841020/357837834 blocks
[root@archbang /]# sudo umount /dev/sda2
[root@archbang /]# sudo fsck /dev/sda2
fsck from util-linux 2.21.2
e2fsck 1.42.4 (12-June-2012)
RootS: clean, 477889/2048000 files, 4606128/8191141 blocks
[root@archbang /]#

Looks good to me. What else can I check? The Wiki says about boot options, but I never fooled with them.

Llama · 2012-07-09 13:51:51

Rollback to

linux-3.3.7-1-i686
linux-headers-3.3.7-1-i686
nvidia-295.53-1-i686
nvidia-utils-295.53-1-i686

solves the problem for the time being.

Links to bug reports or any relevant info will be appreciated .

NB Present state of upgrade, just for reference:

warning: linux: ignoring package upgrade (3.3.7-1 => 3.4.4-2)
warning: linux-headers: ignoring package upgrade (3.3.7-1 => 3.4.4-2)
warning: nvidia: ignoring package upgrade (295.53-1 => 302.17-1)
warning: nvidia-utils: ignoring package upgrade (295.53-1 => 302.17-1)

Last edited by Llama (2012-07-09 15:46:48)

Arch Linux

#1 2012-06-23 10:52:07

Fatal kernel panic (nvidia?)

#2 2012-06-23 13:33:10

Re: Fatal kernel panic (nvidia?)

#3 2012-06-23 19:06:04

Re: Fatal kernel panic (nvidia?)

#4 2012-06-23 19:57:32

Re: Fatal kernel panic (nvidia?)

#5 2012-06-23 20:51:02

Re: Fatal kernel panic (nvidia?)

#6 2012-06-24 07:31:37

Re: Fatal kernel panic (nvidia?)

#7 2012-07-09 13:51:51

Re: Fatal kernel panic (nvidia?)

Board footer