Bug#380188: linux-image-2.6.17-1-686: NULL pointer dereference
On Fri, Dec 26, 2008 at 01:06:43AM +0100, Moritz Muehlenhoff wrote:
> > BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000c
> > printing eip:
> > b01fff1a
> > *pde = 00000000
> > Oops: 0000 [#1]
> > SMP
> > Modules linked in: shpchp pci_hotplug mousedev tsdev sg evdev i2c_piix4 sr_mod i2c_core intel_agp agpgart rtc psmouse snd_es1938 parport_pc serio_raw gameport parport snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device pcspkr snd 8250_pnp floppy soundcore ext3 jbd mbcache ide_generic ide_cd cdrom ide_disk sd_mod piix uhci_hcd usbcore 3c59x mii generic ide_core aic7xxx scsi_transport_spi scsi_mod thermal processor fan
> > CPU: 0
> > EIP: 0060:[<b01fff1a>] Not tainted VLI
> > EFLAGS: 00010206 (2.6.17-1-686 #1)
> > EIP is at uart_write_room+0x9/0x16
> > eax: bf5ff400 ebx: 00000006 ecx: bf6e6a50 edx: 00000000
> > esi: bf6ad000 edi: bf23f000 ebp: 00000006 esp: bf7aff18
> > ds: 007b es: 007b ss: 0068
> > Process S03udev (pid: 1924, threadinfo=bf7ae000 task=bf6e6a50)
> > Stack: b01f4205 bf23f000 bf4d22a0 b01f0433 00000000 bf6e6a50 b0116b57 bf6ad138
> > bf6ad138 00000006 bf6ad000 00000006 00000006 b01f1e6a 00000006 080e9408
> > bf4d22a0 b01f4124 00000000 bf6ad00c bf6ad3e8 b01f27fb bf4d22a0 bf4d22a0
> > Call Trace:
> > <b01f4205> write_chan+0xe1/0x293 <b01f0433> tty_ldisc_try+0x2e/0x33
> > <b0116b57> default_wake_function+0x0/0xc <b01f1e6a> tty_write+0x147/0x1d8
> > <b01f4124> write_chan+0x0/0x293 <b01f27fb> redirected_tty_write+0x1c/0x6c
> > <b01f27df> redirected_tty_write+0x0/0x6c <b0153099> vfs_write+0xa1/0x140
> > <b0153683> sys_write+0x3c/0x63 <b0102b4f> syscall_call+0x7/0xb
> > Code: 09 08 8b 40 10 74 09 81 60 10 ff ff ff fd eb 07 81 48 10 00 00 00 02 8b 5e 68 89 f0 ff 53 2c 5b 5e c3 8b 80 80 01 00 00 8b 50 10 <8b> 42 0c 2b 42 08 48 25 ff 0f 00 00 c3 8b 80 80 01 00 00 8b 50
> > EIP: [<b01fff1a>] uart_write_room+0x9/0x16 SS:ESP 0068:bf7aff18
> >
> > After that, the system hangs.
> >
> > I've downgraded to 2.6.16-2-686, it works.
>
> Does this error still occur with more recent kernel versions?
No, we can probably close this one.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
Reply to: