[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze

2022-03-02 Thread falstaff
It seems that Ubuntu 20.04.4 gets stuck at the same step with the same traces appearing in the kernel log. Since the installer uses the same kernel (5.13) it likely is caused by that kernel version. Ubuntu 22.04 (nightly as of 20220301, which seems to come with 5.15) seems to work fine here. -- Y

[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze

2022-03-02 Thread falstaff
** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze

2022-03-02 Thread falstaff
Similar hang on a T440s trying to install Ubuntu 21.10. The system currently has a fresh Windows 11 copy on half of its SSD hard drive. It seems that ntfsresize causes the kernel to hang. Trying to install Ubuntu gets stuck in Step 4. Install logs attached. Hardware wise, the system seems to work

[Kernel-packages] [Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.

2014-08-03 Thread falstaff
The Kernel installed in our environment is compiled using GCC 4.8.2 (check dmesg | head). Hence I don't think this is related. We had the kernel panic again last week (see attachment). We added the hpwdt module to blacklist, which hopefully works around this problem. We also updated the BIOS, but

[Kernel-packages] [Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.

2014-07-30 Thread falstaff
We see this or a similar issue on a DL360 G7. As visible in the stack trace, we are using VirtualBox. However, I think this is not related since we used the same version on a earlier Kernel. We also upgraded to latest VirtualBox version after the last crash, however the system crashed again since t

[Kernel-packages] [Bug 1348939] [NEW] NETDEV WATCHDOG: eth2 (r8169): transmit queue 0 timed out

2014-07-26 Thread falstaff
Public bug reported: On a server system, I have a r8169 compatible network device running. After getting this kernel warning, communication is not possible anymore. [ 236.943931] [ cut here ] [ 236.943947] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/s