** Bug 62238 has been marked a duplicate of this bug
** Tags added: e1000
** Summary changed:
- IBM T41,42 Regression: Kernel Panic for Suspend/Hibernate
+ e1000 Driver Regression: Kernel Panic on
** Summary changed:
- e1000 Driver Regression: Kernel Panic on
+ e1000 Driver Regression: Kernel
Exactly, well, not exactly, but I'd give it a >95% correlation that X on
fgconsole when rmmod e1000 is typed will cause a panic shortly
thereafter, noting that the rmmod itself does complete successfully and
exits, it's a short time afterwards (long enough for the suspend scripts
to chvt typically)
Just for some further clarification:
If you remove e1000 while in X, the system panics?
If you remove e1000 while not in X, the system doesn't panic?
--
IBM T41,42 Regression: Kernel Panic for Suspend/Hibernate
https://launchpad.net/bugs/62196
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I have the radeon graphics, but as noted earlier the explicit part that
is hanging it up is rmmod of e1000. The NIC on mine does share the same
interrupt assignment as the graphics. I believe I had it hang up with
both the DRI drivers and ATI drivers loaded. Dapper had no such
problems.
--
IBM
Does everyone having this problem have Radeon graphics, or do any of you
have the Intel version of the hardware? I suspect that it's a problem
with the drm module.
--
IBM T41,42 Regression: Kernel Panic for Suspend/Hibernate
https://launchpad.net/bugs/62196
--
ubuntu-bugs mailing list
ubuntu-bu
** Summary changed:
- IBM T41 under Edgy: Kernel Panic for Suspend/Hibernate
+ IBM T41,42 Regression: Kernel Panic for Suspend/Hibernate
** Tags added: ibm kernel panic resume suspend
--
IBM T41,42 Regression: Kernel Panic for Suspend/Hibernate
https://launchpad.net/bugs/62196
--
ubuntu-bugs
