2.2.18 -> 2.2.19 panic

2.2.18 -> 2.2.19 panic

Post by Dirk Emmermache » Wed, 09 May 2001 23:02:37



Hello list,

after upgrade to 2.2.19 on Suse-Linux firewall, I've following message
on booting: VFS: Unable to mount root fs 03:01

What can I do? The System.map file was already copied to /boot...

Thanx in advance.

Best regards.

Dirk Emmermacher
Lowersaxony gymnastics federation

 
 
 

2.2.18 -> 2.2.19 panic

Post by Ketil Klepsvi » Wed, 09 May 2001 23:35:37




> Hello list,

> after upgrade to 2.2.19 on Suse-Linux firewall, I've following message
> on booting: VFS: Unable to mount root fs 03:01

> What can I do? The System.map file was already copied to /boot...

Is this by any chance a scsi system? And have you compiled the scsi
drivers as modules?

K.

Quote:> Best regards.

> Dirk Emmermacher
> Lowersaxony gymnastics federation


 
 
 

2.2.18 -> 2.2.19 panic

Post by Michael Heimin » Thu, 10 May 2001 05:38:15



> Hello list,

> after upgrade to 2.2.19 on Suse-Linux firewall, I've following message
> on booting: VFS: Unable to mount root fs 03:01

> What can I do? The System.map file was already copied to /boot...

Doesn't really matter, it's (mostly) for debugging purposes, read "man
klogd", the
old kernel should just work.

Michael Heiming

 
 
 

2.2.18 -> 2.2.19 panic

Post by Dirk Emmermache » Thu, 10 May 2001 15:19:13


Hello Ketil,

thanx for your answer.




> > Hello list,

> > after upgrade to 2.2.19 on Suse-Linux firewall, I've following message
> > on booting: VFS: Unable to mount root fs 03:01

> > What can I do? The System.map file was already copied to /boot...

> Is this by any chance a scsi system? And have you compiled the scsi
> drivers as modules?

NO. Its not a SCSI-system and scsi drivers are not compiled.
The system is Compaq Deskpro 2000 using  Pentium 133, 64 MB RAM and 1,2
GB HDD. The NICs are 3 3Com 3C900.

Best regards.

Dirk Emmermacher
Lowersaxony gymnastics federation

 
 
 

2.2.18 -> 2.2.19 panic

Post by Dirk Emmermache » Thu, 10 May 2001 15:21:58


Hello Michael,

thanx for your answer.


> Doesn't really matter, it's (mostly) for debugging purposes, read "man
> klogd",

I will do it.

the

Quote:> old kernel should just work.

The old kernel works. A collegue told me, that 2.2.18 is buggy. Is it
really?

Best regards.

Dirk Emmermacher
Lowersaony gymnastics federation

Tel.: +49 511 98097-34
Fax.: +49 511 98097-461

 
 
 

2.2.18 -> 2.2.19 panic

Post by Rasmus B?g Hanse » Thu, 10 May 2001 17:40:10



> > > after upgrade to 2.2.19 on Suse-Linux firewall, I've following message
> > > on booting: VFS: Unable to mount root fs 03:01

> > > What can I do? The System.map file was already copied to /boot...

That does only matter, if the root filesystem gets mounted - it does not
have anything to do with your problem.

Quote:> > Is this by any chance a scsi system? And have you compiled the scsi
> > drivers as modules?

> NO. Its not a SCSI-system and scsi drivers are not compiled.
> The system is Compaq Deskpro 2000 using  Pentium 133, 64 MB RAM and 1,2
> GB HDD. The NICs are 3 3Com 3C900.

Did you include IDE support? IDE/ATA disk support? Did you accidentally
choose the 'old disk-only' driver (although I guess it should work
anyway). Did you compile in support for your root fs (ext2 I assume)?

Rasmus

--
-- [ Rasmus 'M?ffe' B?g Hansen ] --------------------------------------
God put me on earth to accomplish a certain number of things.
Right now I am so far behind I will never die.
                            -Bill Waterson, Calvin and Hobbes
----------------------------------------- [ Remove 'spam' to reply ] --

 
 
 

2.2.18 -> 2.2.19 panic

Post by Dirk Emmermache » Thu, 10 May 2001 17:46:00


Hello Rasmus,

thanx for your answer.

Quote:

> Did you include IDE support?

IDE/ATA disk support?

Yes.

 Did you accidentally

Quote:> choose the 'old disk-only' driver (although I guess it should work
> anyway).

No.

Did you compile in support for your root fs (ext2 I assume)?

Yes.

Best regards.

Dirk

 
 
 

2.2.18 -> 2.2.19 panic

Post by Rasmus B?g Hanse » Thu, 10 May 2001 19:58:19



> > Did you include IDE support?

> IDE/ATA disk support?

> Yes.

/* SNIP - alot of other sounds-like-correct config */

That's strange. What is your root device? Is it hda1 or what. Try
booting the kernel (I assume lilo) with 'linux root=/dev/hd??' (without
quotes of course and your root device in place). Also check your
lilo.conf to check, that the root device is set to the same as the
2.2.17 kernel.

Rasmus

--
-- [ Rasmus 'M?ffe' B?g Hansen ] --------------------------------------
If you only have a hammer
everything looks like a nail
----------------------------------------- [ Remove 'spam' to reply ] --

 
 
 

1. 2.2.18 -> 2.2.19 => no traffic on eth0

Hi!

After upgrading to 2.2.19, neither xosview nor knetload display the
traffic on eth0, but on lo only! On the other hand, iptraf works
perfectly well (but it does not look that good in my panel ;-)). When
using procmeter I get the following:

~$ procmeter
ProcMeter: Unexpected 'ctxt' line in the '/proc/stat' file.
           No context
ProcMeter: Unexpected header line 1 in the '/proc/net/dev' file.
           No lpkt
           No fpkt, fpkt-rx & fpkt-tx
           No spkt, spkt-rx & spkt-tx

while /proc/dev/net looks like this:

Inter-|   Receive                                                |
Transmit
 face |bytes    packets errs drop fifo frame compressed
multicast|bytes    packets errs drop fifo colls carrier compressed
    lo: 1552228    6769    0    0    0     0          0         0
1552228    6769    0    0    0     0       0          0
  eth0:       0  116137    0 1078    0     0          0         0      
0   26081    0    0    0     0       0          0

Whats going wrong here?

Versions are
- xosview 1.7.3
- knetload 1.2
- KDE 1.1.2
- SuSE 6.3

Greetings
Torsten

2. Help with Linux 2.0 booting crash?

3. panic: nonexistent vm area (upgrading 2.2.18 to 2.2.19)

4. how to cp only dot files?

5. USB sound with kernels 2.2.18 / 2.2.19

6. Instance check

7. downgrading from kernel 2.2.19 to 2.2.18

8. modem &rh5

9. 2.2.19 + ide 2.2.19 03252001 patch problem

10. KERNEL PANIC in 2.2.17 and 2.2.18

11. Kernel panic in 2.2.18 and SMP

12. Kernel Panic with LinuxPPC, 2.2.18 and Adaptec AHA2940UW

13. Kernel panic after upgrade from 2.2.16 to 2.2.18