Re: How to debug: "INIT: PANIC: segmentation violation at 0xb776c417! sleeping for 30 seconds."

2011-01-29 Thread Arturo R.
I hate to "bump" my own message, but I'm making some progress and I'm wondering if anyone can help me further debug. My initial message: On Mon, Jan 24, 2011 at 10:31 PM, Arturo R. wrote: > Hi all. > > Per the title, I'd love to get your input on how to debug/fix this > particular issue. A descr

How to debug: "INIT: PANIC: segmentation violation at 0xb776c417! sleeping for 30 seconds."

2011-01-24 Thread Arturo R.
Hi all. Per the title, I'd love to get your input on how to debug/fix this particular issue. A description of my setup: Asus UL30A-X5 Laptop 1.3GHz Intel SU7300 Core 2 Duo 4GB of DDR3 RAM 500GB SATA Intel GMA 4500MHD Running Debian sid on a coLinux 0.7.8 (uname -a: "Linux colinux 2.6.33.5-co-0.7

Re: INIT PANIC

2000-03-20 Thread Oswald Buddenhagen
> The strange thing is that I don't have to give a -t option to > the 'mount' command: > > # mount /dev/wd0p /mnt > > mounts the partition without asking for a fs type. > that's not that surprising. some/most filesystems have an autodetection. > Can I safely unmount /var and run 'fsck' on it?

Re: INIT PANIC

2000-03-20 Thread Horacio MG
> if it's new enough, it would be not that bad - you surely have warranty, > don't you? Yes, Seagate's 3 year warranty! > well - as now all seems to be normal, a hardware failure is a less > probable possibility. i would make a check anyway ... :) optimistical... problems never fade away without

Re: INIT PANIC

2000-03-20 Thread Oswald Buddenhagen
> > > INIT: PANIC: segmentation violation! giving up.. > > > > > > and the booting procedure stopped there, forcing a manual reboot which > > > was successful only after yet another fsck. > > > > > bad trouble is going on ... > > m

Re: INIT PANIC

2000-03-20 Thread Horacio MG
> > INIT: PANIC: segmentation violation! giving up.. > > > > and the booting procedure stopped there, forcing a manual reboot which > > was successful only after yet another fsck. > > > bad trouble is going on ... > make a surface-check of your hdd to see i

Re: INIT PANIC

2000-03-20 Thread Oswald Buddenhagen
> Just a while ago I booted the system, and after a fsck I got the > following message: > > INIT: PANIC: segmentation violation! giving up.. > > and the booting procedure stopped there, forcing a manual reboot which > was successful only after yet another fsck. > &g

INIT PANIC

2000-03-20 Thread Horacio MG
ago I booted the system, and after a fsck I got the following message: INIT: PANIC: segmentation violation! giving up.. and the booting procedure stopped there, forcing a manual reboot which was successful only after yet another fsck. Can anyone tell me what's going on? (Please, send me a C