[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Tags added: testcase -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/611471 Title: Fixup vesafb initialization patch which was mistakenly dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/611471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
This bug was fixed in the package linux - 2.6.31-22.68 --- linux (2.6.31-22.68) karmic-proposed; urgency=low [ Andy Whitcroft ] * SAUCE: docs -- fix doc strings for fc_event_seq [ Brad Figg ] * SAUCE: (no-up) Modularize vesafb -- fix initialization - LP: #611471 [ Chase Douglas ] * SAUCE: sched: update load count only once per cpu in 10 tick update window - LP: #513848 [ Ike Panhc ] * SAUCE: agp/intel: Add second set of PCI-IDs for B43 - LP: #640214 * SAUCE: drm/i915: Add second set of PCI-IDs for B43 - LP: #640214 [ Steve Conklin ] * SAUCE: Fix compile error on ia64, powerpc, and sparc [ Upstream Kernel Changes ] * (pre-stable) x86-32, resume: do a global tlb flush in S4 resume - LP: #531309 * PCI: Ensure we re-enable devices on resume - LP: #566149 -- Steve Conklin sconk...@canonical.com Fri, 22 Oct 2010 09:05:13 -0500 ** Changed in: linux (Ubuntu Karmic) Status: Fix Committed = Fix Released -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed' to 'verification-done'. If verification is not done by Thursday, November 11, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Setting back to v-needed until previous question gets answered. ** Tags added: verification-needed ** Tags removed: verification-done -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Brad, did you actually test the proposed kernel debs from the archive on this hardware? Thanks! -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Tags added: verification-done ** Tags removed: verification-needed -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2 -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
After discussion this was withdrawn from fixing in Hardy. ** Changed in: linux (Ubuntu Hardy) Status: Fix Committed = Won't Fix -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Branch linked: lp:ubuntu/lucid-proposed/linux-mvl-dove -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
This bug was fixed in the package linux - 2.6.32-25.44 --- linux (2.6.32-25.44) lucid-proposed; urgency=low [ Brad Figg ] * SAUCE: (no-up) Modularize vesafb -- fix initialization - LP: #611471 [ Stefan Bader ] * Revert SAUCE: sync before umount to reduce time taken by ext4 umount - LP: #543617, #585092 [ Steve Conklin ] * Revert SAUCE: tulip: Let dmfe handle davicom on non-sparc - LP: #607824 [ Tim Gardner ] * [Config] Added ums-cypress to udeb - LP: #576066 [ Upstream Kernel Changes ] * Revert PCI quirk: Disable MSI on VIA K8T890 systems - LP: #607824 * Revert PCI quirks: disable msi on AMD rs4xx internal gfx bridges - LP: #607824 * Revert (pre-stable) Input: psmouse - reset all types of mice before reconnecting - LP: #607824 * Revert jbd: jbd-debug and jbd2-debug should be writable - LP: #607824 * Revert ext4: Make fsync sync new parent directories in no-journal mode - LP: #615548 * Revert ext4: Fix compat EXT4_IOC_ADD_GROUP - LP: #615548 * Revert ext4: Conditionally define compat ioctl numbers - LP: #615548 * Revert ext4: restart ext4_ext_remove_space() after transaction restart - LP: #615548 * Revert ext4: Clear the EXT4_EOFBLOCKS_FL flag only when warranted - LP: #615548 * Revert ext4: Avoid crashing on NULL ptr dereference on a filesystem error - LP: #615548 * Revert ext4: Use bitops to read/modify i_flags in struct ext4_inode_info - LP: #615548 * Revert ext4: Show journal_checksum option - LP: #615548 * Revert ext4: check for a good block group before loading buddy pages - LP: #615548 * Revert ext4: Prevent creation of files larger than RLIMIT_FSIZE using fallocate - LP: #615548 * Revert ext4: Remove extraneous newlines in ext4_msg() calls - LP: #615548 * Revert ext4: init statistics after journal recovery - LP: #615548 * Revert ext4: clean up inode bitmaps manipulation in ext4_free_inode - LP: #615548 * Revert ext4: Do not zero out uninitialized extents beyond i_size - LP: #615548 * Revert ext4: don't scan/accumulate more pages than mballoc will allocate - LP: #615548 * Revert ext4: stop issuing discards if not supported by device - LP: #615548 * Revert ext4: check s_log_groups_per_flex in online resize code - LP: #615548 * Revert ext4: fix quota accounting in case of fallocate - LP: #615548 * Revert ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode - LP: #615548 * Revert ext4: rename ext4_mb_release_desc() to ext4_mb_unload_buddy() - LP: #615548 * Revert ext4: Remove unnecessary call to ext4_get_group_desc() in mballoc - LP: #615548 * Revert ext4: fix memory leaks in error path handling of ext4_ext_zeroout() - LP: #615548 * Revert ext4: check missed return value in ext4_sync_file() - LP: #615548 * Revert ext4: Issue the discard operation *before* releasing the blocks to be reused - LP: #615548 * Revert ext4: Fix buffer head leaks after calls to ext4_get_inode_loc() - LP: #615548 * Revert ext4: Fix possible lost inode write in no journal mode - LP: #615548 * Revert ext4: Fixed inode allocator to correctly track a flex_bg's used_dirs - LP: #615548 * Revert ext4: Fix estimate of # of blocks needed to write indirect-mapped files - LP: #615548 * Revert ext4: Code cleanup for EXT4_IOC_MOVE_EXT ioctl - LP: #615548 * Revert ext4: Fix the NULL reference in double_down_write_data_sem() - LP: #615548 * Revert ext4: Fix insertion point of extent in mext_insert_across_blocks() - LP: #615548 * Revert ext4: make offset consistent in ext4_check_dir_entry() - LP: #615548 * Revert ext4: Handle non empty on-disk orphan link - LP: #615548 * Revert ext4: explicitly remove inode from orphan list after failed direct io - LP: #615548 * Revert ext4: fix error handling in migrate - LP: #615548 * Revert ext4: Fix fencepost error in chosing choosing group vs file preallocation. - LP: #615548 * Revert ext4: Add flag to files with blocks intentionally past EOF - LP: #615548 * Revert ext4: Fix BUG_ON at fs/buffer.c:652 in no journal mode - LP: #615548 * Revert ext4: Use bitops to read/modify EXT4_I(inode)-i_state - LP: #615548 * Revert ext4: Drop EXT4_GET_BLOCKS_UPDATE_RESERVE_SPACE flag - LP: #615548 * Revert ext4: Fix quota accounting error with fallocate - LP: #615548 * Revert ext4: Handle -EDQUOT error on write - LP: #615548 * Revert ext4: Calculate metadata requirements more accurately - LP: #615548 * Revert ext4: Fix accounting of reserved metadata blocks - LP: #615548 * Revert ext4: Patch up how we claim metadata blocks for quota purposes - LP: #615548 * Revert ext4: Ensure zeroout blocks have no dirty metadata - LP: #615548 * Revert ext4: return correct wbc.nr_to_write in ext4_da_writepages
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Brad, please add a test case. Thanks. -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
We need some testing of the proposed kernel to see whether this has been resolved - please see comment #10 for information about how to get the proposed kernel. Thanks -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Branch linked: lp:ubuntu/linux-mvl-dove -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Discussed with Stefan. This isn't an important bug, doesn't happen on a normal system (we don't remove modules), and if someone could get along with this bug in Jaunty for 16 months, they can certainly get along with it for the remaining two months of its life, so rejecting for jaunty. The risk and overhead for doing a new kernel just for this greatly outweighs the benefit IMHO. The karmic upload fixes other things as well, so it's ok to slip in. ** Also affects: linux (Ubuntu Karmic) Importance: Undecided Status: New -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
The reason I made that upload is that it was discovered that for a long time (Hardy to Maverick were affected) we carried a patch that had dropped parts of the patch which can cause nasty effects on module removal. Since the missing code is all the same for all releases, I was more looking at having a common code base. But I can agree that this is maybe not sufficient for an update in Jaunty which contains only that patch. Especially as Jaunty is reaching end of life soon. -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Also affects: linux (Ubuntu Hardy) Importance: Undecided Status: New -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Changed in: linux (Ubuntu Hardy) Importance: Undecided = Low ** Changed in: linux (Ubuntu Hardy) Status: New = Fix Committed ** Changed in: linux (Ubuntu Karmic) Importance: Undecided = Low ** Changed in: linux (Ubuntu Karmic) Status: New = Fix Committed ** Changed in: linux (Ubuntu Lucid) Importance: Undecided = Low ** Changed in: linux (Ubuntu Lucid) Status: New = Fix Committed -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Accepted linux into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Tags added: verification-needed -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Was released in 2.6.35-18.24 ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Fix Released -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Branch linked: lp:ubuntu/karmic-proposed/linux-mvl-dove ** Branch linked: lp:ubuntu/karmic-proposed/linux-ec2 -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
If it hasn't turned out to be a major problem by now, why do we need to fix this now? I understand lucid, and I also can agree with hardy as LTS, but jaunty and karmic are both rather old/mature already, and not LTS, and thus SRUs there have a diminishing return (likewise, we get very few SRU testing on those). ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
Seems to have been uploaded to jaunty-proposed needs debdiff on bug needs a test case needs approval from ubuntu-sru (subscribed) -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Tags added: kj-triage -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Patch added: Fixes up the vesafb initialization. http://launchpadlibrarian.net/52707334/vesafb.patch -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611471] Re: Fixup vesafb initialization patch which was mistakenly dropped.
** Tags added: patch -- Fixup vesafb initialization patch which was mistakenly dropped. https://bugs.launchpad.net/bugs/611471 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
