Ubuntu goes to kernel panic when I use dhclient

Going to need full dmesg output from this. Not just the last line. Digitial photo of the screen is fine aswell.

What I really need to know is if it affects Dapper. If you could test Flight3 (even the liveCd version is fine), that would be great.

http://cdimage.ubuntulinux.org/releases/dapper/flight-3/

OK. I will take a photo of this problem.

Also, I will probe the Flight3 livecd.

Greetings

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Collins wrote:
> [...]
>
> What I really need to know is if it affects Dapper. If you could test
> Flight3 (even the liveCd version is fine), that would be great.
>
> http://cdimage.ubuntulinux.org/releases/dapper/flight-3/
>

Ben:

Good News!

I tested the liveCD version and this bug don't appear. ;-)

Soon I will send the bug's digital photo. I can't use "dmesg" because my
keyboard don't write after kernel goes to kernel-panic!

Greetings from Chile

- --
Miguel Angel Ruiz Manzano http://people.ubuntu.cl/~mruiz
Computer Science Student - PUCV - Chile
Linux User #323437 PGP key 1024D/0D3FD8A9 2005-06-03

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD1BN1doYiJQ0/2KkRAkTrAKDWH6i0W9sXKq1UD1DrmM44jvTlRQCaAwxb
vHzlNeogkKO/iq9YwvGMqUI=
=onbn
-----END PGP SIGNATURE-----

It could be problem with IMQ. If is this module loaded, or in kernel, then after command "dhclient" without any device, there is kernel panic. I tried it with latest vanila kernel, it is a problem of IMQ. If ubuntu kernel doesnt have IMQ driver, then please ingnore, or delete this post.

i am not really rejecting the bug, its just that once it has been sorted to the right component (the kernel in this case) the ubuntu bit is meant to rejected. it feels so rude.

Will this be corrected for breezy? If not, we can just close this bug for it, as it was already done for dapper...

I get exactly the same error but when syncing 2 ide disks (maxtor) in a software-raid1 device, which are both connected to the same pdc20267 (promise) at exactly the time of completion of syncing the raid-device.

this error is repeatable. every time the device finishes syncing, the kernel panics.

any ideas how to narrow this one down? my guess is a kernel bug.

Installing Ubuntu 5.0 system stalled with blank screen. Rebooting and attempting to continue installation stops and reads:
[42944668.265000] (0) Kernal panic-not syncing: attempt to kill init.
Next line is:
[42944668.265000] blank with a blinking curser, keyboard ineffective

System is an empty 40 Gig HD, tried formatted and unformatted, AMD Anthalon CPU with 750+ MB ram.

Marking as confirmed, since it was complete enough to fix 2.6.15. :-)

We are closing this bug report as it concerns the 2.6.12 kernel from Breezy which is no longer supported. However, please reopen it if it is still an issue with a supported version of Ubuntu and feel free to submit bug reports in the future.