On Tue, 2004-10-26 at 23:22 -0400, William Ballard wrote:
> I have an external USB 2.0 2.5" hard drive, shows up as /dev/sda, with
> an ReiserFS partition. If I yank it with it mounted ReiserJS panics.
> I have the fstab entry marked as sync, rw.
>
> I don't have PCI Hotplugging installed, but I
I have an external USB 2.0 2.5" hard drive, shows up as /dev/sda, with
an ReiserFS partition. If I yank it with it mounted ReiserJS panics.
I have the fstab entry marked as sync, rw.
I don't have PCI Hotplugging installed, but I do a lot of USB
hotplugging.
Has anyone had any experience with t
On Thu, 21 Oct 2004 09:22:40 + (UTC), Alexis Huxley <[EMAIL PROTECTED]> wrote:
> > How do I interpret 03:04? If I boot off the boot floppy, everything is
>
> It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld
> /dev/hda4' to see this).
>
> > fine. Have poked around for an
> How do I interpret 03:04? If I boot off the boot floppy, everything is
It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld
/dev/hda4' to see this).
> fine. Have poked around for answers in the archives, but haven't
> figured it out.
>
> boot drive:
> hda1 - /boot
> hda2 - sw
Had a power outage, and when I brought my Debian 3 system back up it was
hosed:
---
EXT2-fs: unable to read superblock
Attempt to access beyond device
.
.
.
FAT bread failed
Invalid session number or type of track
.
.
.
Kernel panic: VFS: unable to mount root fs on 03:04
---
How
lated to aic7xxx, but it boots and runs
fine.
o When I install 2.6.8 I get a kernel panic. Fairly early in the boot
process (before all the drive info shows up) I get:
pivot_root: Np such file or directory
/sbin/init: 426: Cannot open /dev/console: no such file
Kernel panic: Attempted to kill ini
> Then the machine rebooted itself and it has come up
> with a kernel panic. My guess is that this is related
> to some problem with the bootloader or LILO. I was
> just hoping that someone could refer me to a likely
> fix for this since I'm not even in the city with the
>
up
with a kernel panic. My guess is that this is related
to some problem with the bootloader or LILO. I was
just hoping that someone could refer me to a likely
fix for this since I'm not even in the city with the
machine and I have to forward this to my partner who
helps to run it so that he
Stefan O'Rear wrote:
Size. The bad initrds are more than 2MB uncompressed. Try passing
ramdisk_size=8192 to the kernel prompt. (Loop mounting won't detect
this).
Many thanks.
-
DISCLAIMER: This email is bound by the terms and conditions described at
http://ww
On Tue, Sep 14, 2004 at 09:17:57AM -0700, Russel Hill wrote:
> We routinely build ISO's and occasionally one fails to boot (with a
> kernel panic). I've attached a screenshot of the kernel panic.
>
> The ISO's are all built using script files and they are always built
We routinely build ISO's and occasionally one fails to boot (with a
kernel panic). I've attached a screenshot of the kernel panic.
The ISO's are all built using script files and they are always built the
same way. They may include new packages but the boot image is built the
indication it happened.
That interrupt is unrelated to the system hang,
So you are telling me that the the error I receive (that is "BAD EIP:
spurious...etc") is not related to the kernel panic,aren't you?
I read somewhere during my googling there's a tool that can make a du
Justin Guerin wrote:
Would you be willing to try installing Sarge?
I'm strongly considering to wait for the next Stable before
installing.In these days I also tried to run some Deb-based
distributions (Knoppix 3.3 Live Cd,Morphix and Progeny),but no one
installs.Slack 10.0 does it (with the b
Pigeon wrote:
Try turning off the APIC in the BIOS setup rather than in the kernel.
I had something similar once and this got it going.
Tried.No way!
Thnx anyway
Lorenzo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Sep 09, 2004 at 05:32:54PM +0200, Lorenzo Cuciniello wrote:
> Hi!
> John Summerfield wrote:
> >Lorenzo Cuciniello wrote:
> >
> >The two events are unrelated. The spurious interrupts have been going on
> >for years. Not that I can locate one just now, but a little googling
> >should clear
kernel loading.
> The error is:
> *
> Spurious 8259A interrupt:IRQ7
> kernel panic!
> attempt to kill init
> **
Try switching to the message console (Alt-F3, I think. Check before you
boot). When the freeze occurs, you may get a more informative error
messa
Lorenzo Cuciniello wrote:
Hi!
John Summerfield wrote:
Lorenzo Cuciniello wrote:
The two events are unrelated. The spurious interrupts have been going
on for years. Not that I can locate one just now, but a little
googling should clear that point up.
Thanks for your answer.I've googled searching
Hi!
John Summerfield wrote:
Lorenzo Cuciniello wrote:
The two events are unrelated. The spurious interrupts have been going on
for years. Not that I can locate one just now, but a little googling
should clear that point up.
Thanks for your answer.I've googled searching for "spurious
interrupt",b
(solving it with a simple dmesg),but none during
the install process.
Briefly, my problem is that I cannot install Woody (3.0r2) with
precompiled bf24 kernel image on my machine,because of this error
after the first kernel loading.
The error is:
*
Spurious 8259A interrupt:IRQ7
kernel panic
),but none during the
install process.
Briefly, my problem is that I cannot install Woody (3.0r2) with
precompiled bf24 kernel image on my machine,because of this error after
the first kernel loading.
The error is:
*
Spurious 8259A interrupt:IRQ7
kernel panic!
attempt to kill init
geekboy wrote:
Martin Dickopp wrote:
freeing initrd memory: 3956k freed
FAT: bogus logical sectro size 0
kernel panic: VFS : unable to mount root fs on 03:05
So the initrd.img is working. remembered to run lilo after upgrade.
does the 03:05 mean the fat partition on hda3 is screwed?
No, 03:05
Martin Dickopp wrote:
freeing initrd memory: 3956k freed
FAT: bogus logical sectro size 0
kernel panic: VFS : unable to mount root fs on 03:05
So the initrd.img is working. remembered to run lilo after upgrade.
does the 03:05 mean the fat partition on hda3 is screwed?
No, 03:05 refers to
geekboy <[EMAIL PROTECTED]> writes:
> Just tried upgrading my kernel from knoppix 2.4.22xfs to 2.4.26-1-k7
> while booting it grinds to a halt with error:
>
> freeing initrd memory: 3956k freed
> FAT: bogus logical sectro size 0
> kernel panic: VFS : unable to mount roo
Just tried upgrading my kernel from knoppix 2.4.22xfs to 2.4.26-1-k7
while booting it grinds to a halt with error:
freeing initrd memory: 3956k freed
FAT: bogus logical sectro size 0
kernel panic: VFS : unable to mount root fs on 03:05
So the initrd.img is working. remembered to run lilo after
<[EMAIL PROTECTED]>
Fecha: Domingo, Agosto 15, 2004 4:52 pm
Asunto: Re: Kernel panic (customizing kernel 2.6.6)
> On Sun, Aug 15, 2004 at 03:13:39PM -0600, Marvin Gerardo Aguero
> Salazar wrote:
>
> > My theory is that the problem relies in the file called
> > initrd.img-
On Sunday 15 August 2004 01:13 pm, Marvin Gerardo Aguero Salazar wrote:
> Guys,
>
> I am trying to customize my kernel 2.6.6 but it fails to boot. I have
> a theory of why it is not booting, but I don't know how to fix it.
>
> Let's see, I first downloaded and installed kernel-2.6.6-1-386 and
> ins
On Sun, Aug 15, 2004 at 03:13:39PM -0600, Marvin Gerardo Aguero Salazar wrote:
> My theory is that the problem relies in the file called
> initrd.img-2.6.6-1-386. Since the make process didn't create a
> initrd.img-2.6.6 I kept the same one.
You might look at mkinitrd. You might also wonder (as
Guys,
I am trying to customize my kernel 2.6.6 but it fails to boot. I have a
theory of why it is not booting, but I don't know how to fix it.
Let's see, I first downloaded and installed kernel-2.6.6-1-386 and
installed it just fine. I have a directory called /lib/modules/2.6.6-1-386.
Then I dow
le does not exist.
mount: /dev2/root2 is not a valid block device
-> This message is displayed 8 times.
pivot_root: No such file or directory
/sbin/init: 348: cannot open dev/console: No such file
kernel panic: Attempted to kill init!
Any ideas of what I have done wrong here?
Does anyone know wh
: No such file or directory
/sbin/init: 348: cannot open dev/console: No such file
kernel panic: Attempted to kill init!
Any ideas of what I have done wrong here?
Does anyone know what is going on here and how to fix it?
TIA,
-Marvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
ke modules
> make modules_install
> make install
>
> ---
> VFS: Cannot open root device "301" or
> unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown
&
George Roman wrote:
than i don't know what it is. sorry. have you tried other kernel versions
before 2.6.3? make sure that you didn't use module in front of ext2. if
you did so, install module-init-tools or use builtin option. if you did
so, there is nothing elese i could help.
Also check that your
than i don't know what it is. sorry. have you tried other kernel versions
before 2.6.3? make sure that you didn't use module in front of ext2. if
you did so, install module-init-tools or use builtin option. if you did
so, there is nothing elese i could help.
George Roman
Technical Support
RDS Ti
I have seen this error when in-compatible/correct options
chosen during config. So, bite the bullet and redo the
kernel compliation from scratch!
-ishwar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Check out that you have the right partition type enabled in Advanced
partion types, it's a bit hidden in the options tree. (under xconfig
filesystem->partition types->advanced partition types->pc bios)
For a pc type, it would be the
MSDOS_PARTITION
option. It's absolutely necessary for the kerne
--- Stelian Iancu <[EMAIL PROTECTED]> wrote:
> Check out that the fs that the root partition has is
> NOT build as a
> module for the kernel, but in the kernel itself.
The root filesystem is the ext2 filesystem and it is
build in the kernel. I use xconfig to configure and I
clearly remembers that
On Thu, 24 Jun 2004 05:21:13 -0700 (PDT), Ajitabh Pandey
<[EMAIL PROTECTED]> wrote:
>
> --- George Roman <[EMAIL PROTECTED]> wrote:
> > i think that in lilo (grub) you haven't specified
> > the corect root
> > partition.
>
> The older image is working fine as the lilo.conf has
> this entry in a
--- George Roman <[EMAIL PROTECTED]> wrote:
> i think that in lilo (grub) you haven't specified
> the corect root
> partition.
The older image is working fine as the lilo.conf has
this entry in a common area immediately after the
boot= entry.
So without this entry it should also work. But
> make bzImage
> make modules
> make modules_install
> make install
>
> ---
> VFS: Cannot open root device "301" or
> unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to
dep
make clean
make bzImage
make modules
make modules_install
make install
---
VFS: Cannot open root device "301" or
unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs
On Friday 18 June 2004 13:36, Chris Metzler wrote:
> On Fri, 18 Jun 2004 14:43:49 -0400
>
> Derrick 'dman' Hudson <[EMAIL PROTECTED]> wrote:
> > On Fri, Jun 11, 2004 at 02:45:36PM +1000, glenn wrote:
> > | When i boot off this image I get a kernel panic, fol
On Fri, Jun 11, 2004 at 02:45:36PM +1000, glenn wrote:
| When i boot off this image I get a kernel panic, following a message
| from sbin/init, that it cant find dev/console.
|
| Any ideas what I have to do?
|
| incidentally, ls -l /dev/console gives :
| crwx-- 1 root tty 5, 1 Jun 11:14:40
On Fri, 18 Jun 2004 14:43:49 -0400
Derrick 'dman' Hudson <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 11, 2004 at 02:45:36PM +1000, glenn wrote:
>
> | When i boot off this image I get a kernel panic, following a message
> | from sbin/init, that it cant find dev/con
howdy all
I've got a box with a custom 2.4.18 kernel (customed to use some funny
hardware, and win4lin). I no longer need the customizations, and wanted
to upgrade 2.6 - so installed 2.6.6 kernel image.
When i boot off this image I get a kernel panic, following a message
from sbin/init, th
Ishwar Rattan wrote:
Where can I get 2.6.6-debian kernel sources or kernel-image deb?
-ishwar
On Mon, 31 May 2004, Ralph Bergmann wrote:
Also try
apt-cache search kernel- will give you many options. You might want to
check around on apt-cache search to see how to fine tune it.
--
To UNSUBSCRI
Ishwar Rattan wrote:
Where can I get 2.6.6-debian kernel sources or kernel-image deb?
-ishwar
On Mon, 31 May 2004, Ralph Bergmann wrote:
In Debian the name of the packages you want to install are
kernel-image-2.6.6 . I have an athlon so mine is kernel-image-2.6.6-1-k7
. The lazy way to do it i
Where can I get 2.6.6-debian kernel sources or kernel-image deb?
-ishwar
On Mon, 31 May 2004, Ralph Bergmann wrote:
> Hello!
>
> If I use the 2.6.6 kernel, I get a "Kernel panic" when starting.
>
> I use a Debian unstable, last update 31.Mai 2004.
>
> Kernel:
Hello!
If I use the 2.6.6 kernel, I get a "Kernel panic" when starting.
I use a Debian unstable, last update 31.Mai 2004.
Kernel:
kernel-image-2.6.6-1-686-smp
System:
:00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 05)
:00:00.1 Host bridge: ServerWorks CNB20LE Host B
On Mon, May 24, 2004 at 05:54:59PM -0700, [EMAIL PROTECTED] wrote:
>
> So what you are saying is that what I did is fine? So why do I get this
> kernel panic error???
If the new kernel has built in, as opposed to modules, for everything
that is required to boot then I don't kn
d using the 2.6 kernel. The kernel that came with it runs
>>>fine, but I compiled and installed a new kernel and it will not run.
>>>When
>>>I boot to it, it complains :
>>>VFS: Cannot open root device "hda3" or unknown-block(0,0)
>>>Please app
On Mon, May 24, 2004 at 08:59:21AM -0700, [EMAIL PROTECTED] wrote:
> >
> You are correct, the 2.6.5 is the new one.
> I did not use any flags I just did a make-kpkg kernel_image and a dpkg -i
> I noticed that the new boot loader menu items didn't have the initrd
> lines, is that required. I didn't
the sarge
> net install cd using the 2.6 kernel. The kernel that came with it runs
> fine, but I compiled and installed a new kernel and it will not run. When
> I boot to it, it complains :
> VFS: Cannot open root device "hda3" or unknown-block(0,0)
> Please append a correct
fine, but I compiled and installed a new kernel and it will not run. When
I boot to it, it complains :
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
By the way:
Thx, ill talk to them, sorry for the delay in the answer,
i just had some things to do.
Cheers,
rak
On Wed, May 12, 2004 at 05:23:05PM +0200, LeVA wrote:
> Maybe the guys at [EMAIL PROTECTED] could help you.
>
> Best wishes,
>
> Daniel
>
> --
> LeVA
>
--
To UNSUBSCRIBE, email to
Maybe the guys at [EMAIL PROTECTED] could help you.
Best wishes,
Daniel
--
LeVA
pgp0.pgp
Description: signature
hi ppl,
I got this strange message on console today when i came to work,
the machine is running sarge fresh upgrade from woody, the kernel is
2.4.21, but i'm about to upgrade it
The message in the console was this:
<1>Unable to handle kernel NULL pointer derefernce at virtual address 0008
p
9)
Please append a correct "root=" boot option
Kernel panic: VFS:Unable to mount root fs on unknown-block (3,69)"
Tux:~# df
Filesystem1K-blocks Used AvailableUse Mounted on
/dev/hdb5 13690082183251079997 17% /
tmpfs
2.6.5 but in the
> boot process i get this:
>
> Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
Did you include support for your ide/scsi controller IN the kernel, too?
--
Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC?
Words of th
=/dev/hda3 ro
Savedefault
Boot
My new kernel is compiled with ext2, ext3 and the others also.
My filesystem is ext3.
When i reboot my system i can choose to boot the debian2.6.5 but in the
boot process i get this:
Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
How can i fix it so
Boot
My new kernel is compiled with ext2, ext3 and the others also.
My filesystem is ext3.
When i reboot my system i can choose to boot the debian2.6.5 but in the
boot process i get this:
Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
How can i fix it so that i can boot with my
Monday 29 March 2004 12:54, [EMAIL PROTECTED]
wrote:
> I just installed the 2.4.16 686 kernel image and now when I boot I get
> these messages
> request_module[block-major-3]: root fs not mounted
> VFS: cannot open root device "hda8" or 3:08
> Please append a correct &quo
nd a correct "root=" boot option
> Kernel Panic: VFS Unable to mount root fs on 3:08
I don't suppose you changed your bootloader at the
same time, did you? It sounds like you switched to
grub and neglected to pass the necessary kernel
arguments.
If this is indeed the case
I just installed the 2.4.16 686 kernel image and now when I
boot I get these messages
request_module[block-major-3]: root fs not
mounted
VFS: cannot open root device "hda8" or 3:08
Please append a correct "root=" boot option
Kernel Panic: VFS Unable to mount root fs on
TED]>) wrote:
> > Debian - unstable
> >
> > The PC has not been used for couple weeks. On booting it went 'kernel
> > panic' with following warning;
> > ..
> > ...
> > modprobe : modprobe: can't locate module block-major-3
> >
Hello
Stephen Liu (<[EMAIL PROTECTED]>) wrote:
> Debian - unstable
>
> The PC has not been used for couple weeks. On booting it went 'kernel
> panic' with following warning;
> ..
> ...
> modprobe : modprobe: can't locate module block-m
Hi folks,
Debian - unstable
The PC has not been used for couple weeks. On booting it went 'kernel panic'
with following warning;
..
...
modprobe : modprobe: can't locate module block-major-3
mount: dev2/root2 is not a valid block device
mount: you must specify
On Sun, 2004-03-07 at 19:24, la2 wrote:
> Hello debian-user,
>
> HELP!
> I compiled kernel 2.4.18, Installed it.
> When I try to boot, it prints : "kernel panic: VFS: cannot mount root
> on 03:06".
> My MBR is on /dev/hda, Debian is on /dev/hda6.
> B
Hello
la2 (<[EMAIL PROTECTED]>) wrote:
> I compiled kernel 2.4.18, Installed it.
> When I try to boot, it prints : "kernel panic: VFS: cannot mount
> root on 03:06".
> My MBR is on /dev/hda, Debian is on /dev/hda6.
> BTW before when i compiled the sam
Hello debian-user,
HELP!
I compiled kernel 2.4.18, Installed it.
When I try to boot, it prints : "kernel panic: VFS: cannot mount root
on 03:06".
My MBR is on /dev/hda, Debian is on /dev/hda6.
BTW before when i compiled the same kernel all had succeded.
--
Best reg
When installing kernel images, the installer first give a lengthy warning
about initrds. If one continues, it offers to wipe out your old lilo, etc.
Word to the wize: DON'T.
After installation is done, leaving lilo alone: Edit lilo.conf and add the new
kernel image and its initrd to the bootup
[EMAIL PROTECTED] wrote:
Yes. Your simplest option (going from memory here) is to boot off the CD
again, choose the bf24 kernel, skip the majority of the configuration
options, opting instead for mount previous installation, install lilo, and
reboot - then you should be back in bussiness.
NOTE: I'm
nsible for these components.
>
> So, to make a long story short, I'm unable to boot into my Woody
> server, with the newly installed kernel. I tried the rescue disk, but
> it gives me a kernel panic. I tried the 'shift-tab' sequence at the
> lilo prompt, and it only
>Yes, however, I didn't delete anything... When I was working in Lilo previous
to
>the 'accident', the old config was there. Beats me what happened to it. It
was
>called 'Linux.old'
Generally, it's a wise idea, not to touch lilo.conf anymore unless You have
to. The debian-way is to move Your
Jonathan Schmitt wrote:
> You should always keep the old kernel in Your bootmenu to prevent such things,
> this is, what the construct with /vmlinuz and /vmlinuz.old is for.
Yes, however, I didn't delete anything... When I was working in Lilo previous to
the 'accident', the old config was there
Jonathan Schmitt wrote:
Hallo
So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards.
Lilo
gave an error on the stanza I added to lilo as per the debian installer
instructions: I think it was the 'initrd=/initrd.img' line. I obviously added
it
to the wrong place.
You s
Hallo
>So, I took the plunge and installed '2.4.18.img' and ran lilo afterwards.
Lilo
>gave an error on the stanza I added to lilo as per the debian installer
>instructions: I think it was the 'initrd=/initrd.img' line. I obviously added
it
>to the wrong place.
You should always keep the old
ponsible for these components.
So, to make a long story short, I'm unable to boot into my Woody
server, with the newly installed kernel. I tried the rescue disk, but
it gives me a kernel panic. I tried the 'shift-tab' sequence at the
lilo prompt, and it only gives me one kernel choi
e components.
So, to make a long story short, I'm unable to boot into my Woody server, with
the newly installed kernel. I tried the rescue disk, but it gives me a kernel
panic. I tried the 'shift-tab' sequence at the lilo prompt, and it only gives me
one kernel choice -- I can&#x
dpkg --install debhelper_4.2.4_all.deb
RESULT: kernel panic + full lock-up.
-
dpkg LOOKS CORRUPT:
-
stokes:/var/cache/apt/archives# dpkg --list
dpkg-query: parse error, in file `/var/lib/dpkg/available' near line 1:
newline in field name `125c81'
stokes:/var/cache/apt/archives
One more thing I tried last night. I created the bf24 boot
floppies from the debian 3.0r1 CD but got a kernel panic. I
also downloaded the unstable boot floppies from one of the
debian primary sites and again got a kernel panic. Why would
the floppy kernel fail to boot?
- Message Forwarded
On Thu, Feb 05, 2004 at 09:54:15PM -0800, Kenward Vaughan wrote:
> > Rebooting fixes it. I've only had it do this after idle time (but I'm
> > probably always running spamassassin on incoming mail.)
> >
> > I'm running testing with no backports from unstable or anything like
> > that.
>
> Power m
On Thu, Feb 05, 2004 at 11:41:06AM -0500, Brett Carrington wrote:
> On Thu, Feb 05, 2004 at 06:02:51PM +0200, Micha Feigin wrote:
> > On Thu, Feb 05, 2004 at 07:07:11AM -0500, Brett Carrington wrote:
> > > A few days after I upgraded to the 2.6 tree (using debian's precompiled
> > > packages) somet
On Thu, Feb 05, 2004 at 10:45:31PM +0200, Micha Feigin wrote:
> I am not sure if its going to catch anything but you may try running
> top in a visible window when you leave your computer.
> If you computer locks up you will get a list of the active processes
> (probably not all since there will be
On Thu, Feb 05, 2004 at 11:41:06AM -0500, Brett Carrington wrote:
> On Thu, Feb 05, 2004 at 06:02:51PM +0200, Micha Feigin wrote:
> > On Thu, Feb 05, 2004 at 07:07:11AM -0500, Brett Carrington wrote:
> > > A few days after I upgraded to the 2.6 tree (using debian's precompiled
> > > packages) somet
On Thu, Feb 05, 2004 at 06:02:51PM +0200, Micha Feigin wrote:
> On Thu, Feb 05, 2004 at 07:07:11AM -0500, Brett Carrington wrote:
> > A few days after I upgraded to the 2.6 tree (using debian's precompiled
> > packages) something very bad happened.
> >
> > I'm not very knowledgable about this kind
On Thu, Feb 05, 2004 at 07:07:11AM -0500, Brett Carrington wrote:
> A few days after I upgraded to the 2.6 tree (using debian's precompiled
> packages) something very bad happened.
>
> I left my box idle for a while, came back, and nothing would work.
> Well, kind of:
>
>
> # any command
> Segme
On 2004-02-05, Brett Carrington penned:
>
> --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> A few days after I upgraded to the 2.6 tree (using debian's
> precompiled packages) something very bad happened.
>
> I left my box idle for a while, came back,
A few days after I upgraded to the 2.6 tree (using debian's precompiled
packages) something very bad happened.
I left my box idle for a while, came back, and nothing would work.
Well, kind of:
# any command
Segmentation fault.
# any other command
Segementation fault.
I had mutt and screen runni
-0300, Toshiro wrote:
>> Hello,
>> I tried to upgrade from 2.4 to this 2.6 package and I get a kernel panic
>> with the following message:
>> RAMDISK cramfs filesystem found 4184kb image too big (it wants 4096 or
>> something like that)
>> then I get the VFS cannot
> Hello,
> I tried to upgrade from 2.4 to this 2.6 package and I get a kernel panic
> with the following message:
> RAMDISK cramfs filesystem found 4184kb image too big (it wants 4096 or
> something like that)
> then I get the VFS cannot open root device ..
> I was thus w
Whew! I though it was just me.
I get the same thing with just the k7 flavour... the standard i386
version works me so the i386-smp flavour might work for you.
I filed a bug using the reportbug tool but it hasn't shown up in the
bug tracking system yet. It was the first time I used that tool so I
Hello,
I tried to upgrade from 2.4 to this 2.6 package and I get a kernel panic
with the following message:
RAMDISK cramfs filesystem found 4184kb image too big (it wants 4096 or
something like that)
then I get the VFS cannot open root device ..
I was thus wondering if there was a way to get
((unsigned char*)regs->eip)[i])) {
238 bad:
239 printk(" Bad EIP value.");
240 break;
241 }
242 printk("%02x ", c);
243 }
244 }
The numbe
Hi
I have a problem installing woody on my new Asus P4P8X board.
when I start from cd and enter bf24 at the promt, it will try to
start, till it gets to the HDD's. Then I get some numbers,
Bad EIP Value and Kernel Panic??? is there anybody who
can tell me what that means???
If I start K
Roberto Sanchez wrote:
> HFS is the apple file system. Was the CD burned on a Mac? Maybe
> you do not all the necessarf stuff to support the HFS filesystem.
> It could also be a kernel bug.. Interesting.
>
The disk is mounted as an iso9660 disk. The same CD contains installers
for Windows, L
questions the installer starts to work and immediately causes a kernel
panic.
If there is anything else I can provide to help debug this problem,
please ask.
Thanks,
Jonathan Brandmeyer
The kernel's last words to the console:
hfs_fs: unable to locate alternate MDB
hfs_fs: continuing witho
starts to work and immediately causes a kernel
panic.
If there is anything else I can provide to help debug this problem,
please ask.
Thanks,
Jonathan Brandmeyer
The kernel's last words to the console:
hfs_fs: unable to locate alternate MDB
hfs_fs: continuing without an alternate MDB
h
will shed more light on the problem.
Regards,
Anim
> Subject: FW: FW: Kernel panic error
>
>
>
>
> > > From: Jerome R. Acks
> > > [mailto:[EMAIL PROTECTED]
> > > Sent: 24 October 2003 03:47
> > > To: Anim Asante
> > >
Brent Miller wrote:
This may be a longshot, but are you using a wireless networking card?
I get the same kp when using linux-wlan-ng with some netgear NICs
under heavy load.
-Brent
No sorry, I'm using a simple realtek 8139 NIC, and yes I know it's cheap
but the 3coms I had before gave me way mor
ca738380
> 010a cecf9560 cecf9698 0006 cf3d1dd4 c01c1c8e cecf9560 ca738380
>
> Calltrace: [] [] [] []
> []
> [] [] [] [] []
> []
> [] [] [] [] []
> []
> [] [] [] []
>
> Code : 39 16 0f 94 c0 0f b6 c0 ba 01 00 00 00 85 c0 0f 45 54 24 24
>
> <0> Kernel panic: Aiee, killing interrupt handler!
> I
401 - 500 of 1036 matches
Mail list logo
