Re: reading /proc/ioports causes OOPS

[Nikola Ciprich]

> My guess is that some module got unloaded and didn't unregister its
> ioport reservation, causing a segfault when the kernel tries to read
> the description string. Can you post the full dmesg output from
> bootup up to this point?
Hi, sure,
here it is: http://nelide.cz/downloads/dmesg.log
I see [last_unloaded]: freq_table there, loading the module back doesn't 
fix the problem. I could reboot the machine on wednesday, so I can try
reading /proc/ioports just after reboot to see if there is any change...
nik

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@xxxxxxxxxxx
-------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/