[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2009-01-30 Thread Michele Mangili
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-08-28 Thread Leann Ogasawara
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-08 Thread Roland Arendes
OK - disregard what I wrote above. s/hardy/gutsy/. I mixed up the codenames of Ubuntu. I was and I am talking about the current stable Ubuntu Server edition (codenamed Gutsy). Thats were I can reproduce the bug. I did NOT test it on any unstable (hardy) release. That however brings me back to

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Ralph Janke
Thanks for reporting this issue. Would it be possible to test this issue against the latest hardy kernel and tell us if it still occurs? Thanks. ** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: (unassigned) = Ralph Janke (txwikinger) Status: New = Incomplete -- Kernel Oops

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Roland Arendes
Yes, its possible - if you tell me how exactly I can do that. I guess I have to change some lines in apt.conf and update a specific package? Sorry, I'm not very experienced with ubuntu and apt-get in general (yet). -- Kernel Oops NULL Pointer dereference on i2o_proc

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Roland Arendes
Nevermind. I just noticed that I'm already using hardy and that its not the codename for the unstable version. I'll apt-get update apt-get upgrade right away, hold on.. -- Kernel Oops NULL Pointer dereference on i2o_proc https://bugs.launchpad.net/bugs/191688 You received this bug notification

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Roland Arendes
I already were at the current hardy kernel. I can confirm this bug on: ii linux-image-2.6.22-14-se 2.6.22-14.52 Linux kernel image for version 2.6.22 on x86/x86_64 ii linux-image-server 2.6.22.14.21 Linux kernel image on Server Equipment. ii linux-server

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Ralph Janke
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- Kernel Oops NULL Pointer dereference on i2o_proc https://bugs.launchpad.net/bugs/191688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Ralph Janke
It would be great if you could run the following commands and attach the resulting files: uname -a uname-a.log cat /proc/version_signature version.log dmesg dmesg.log sudo lspci -vvnn lspci-vvnn.log Thanks. ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Changed in:

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Roland Arendes
uname -a Linux geminus 2.6.22-14-server #1 SMP Tue Feb 12 08:27:05 UTC 2008 i686 GNU/Linux cat /proc/version_signature Ubuntu 2.6.22-14.52-server ** Attachment added: dmesg.log http://launchpadlibrarian.net/12471101/dmesg.log -- Kernel Oops NULL Pointer dereference on i2o_proc

[Bug 191688] Re: Kernel Oops NULL Pointer dereference on i2o_proc

2008-03-06 Thread Roland Arendes
** Attachment added: lspci-n.log http://launchpadlibrarian.net/12471102/lspci-n.log -- Kernel Oops NULL Pointer dereference on i2o_proc https://bugs.launchpad.net/bugs/191688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.