[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-22 Thread Avery-yates
with 6.8-31 I was able to install 24.04 ubuntu-server-minimal with zfs boot & root using the OpenZFS tutorial for 22.04 with minimal change. Since there's no ZFS root install script in subiquity yet the OpenZFS instructions are going to be the go-to for many people again. https://github.com/openz

[Kernel-packages] [Bug 986805] Re: WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()

2013-12-28 Thread Avery-yates
** Changed in: linux (Ubuntu) Status: Invalid => Incomplete -- 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/986805 Title: WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generi

[Kernel-packages] [Bug 986805] Re: WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()

2013-12-28 Thread Avery-yates
It still happened and both cases are related. I don't see why this has to be closed. Other people reported the same issue, they didn't have the same hardware. There is no reason to close this because it happened on more than one of my computers. This bug not being hardware specific is a potentia

[Kernel-packages] [Bug 986805] Re: WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()

2013-12-28 Thread Avery-yates
And this is where I fall flat on my ass. 3days ago when my nic gave out , I googled the error. This part : "/build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()" To see if I found anything on what happened. I was somewhat surprised I ended up at a bug report I filed

[Kernel-packages] [Bug 986805] Re: WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()

2013-12-27 Thread Avery-yates
Well , it happened to me again today. More than a year later but this time it didn't recover the nic gave out. To the OS however on IP level everything was hunky doori. I was able to issue ping commands over the interface , no replies of course. anyway , here is the entry in the log. I had to r