Bug#293430: matrox frame buffer console: mode switching broken
Package: kernel-image-2.6.8-2-386 Version: 2.6.8-13 When using the Matrox frame buffer driver and switching between consoles of different resolution, the mode timings get messed up. How to reproduce the problem: - if you are still in text mode, load the framebuffer modules: # modprobe matroxfb_base; modprobe fbcon - set a higher resolution mode on the first console only (this is my custom mode, I will show the timings below) # fbset 1024x640-85 # fbset mode 1024x640-85 # D: 77.682 MHz, H: 57.119 kHz, V: 84.999 Hz geometry 1024 640 1024 1600 8 timings 12873 168 56 28 1 112 3 accel true rgba 8/0,8/0,8/0,0/0 endmode - switch to another console: press Alt+F2 - switch back to console 1: press Alt+F1 - you will see the following output: matroxfb: cannot set xres to 1400, rounded up to 1664 matroxfb: cannot set xres to 1400, rounded up to 1664 matroxfb: cannot set xres to 1400, rounded up to 1664 matroxfb: cannot set xres to 1600, rounded up to 1664 matroxfb: cannot set xres to 1600, rounded up to 1664 matroxfb: cannot set xres to 1600, rounded up to 1664 matroxfb: cannot set xres to 1600, rounded up to 1664 matroxfb: cannot set xres to 1800, rounded up to 1920 matroxfb: cannot set xres to 1800, rounded up to 1920 - The image looks interlaced, and indeed it is. The timings and geometry have also changed: # fbset mode 1024x768-87 # D: 44.901 MHz, H: 35.523 kHz, V: 86.960 Hz geometry 1024 768 1024 768 8 timings 22271 56 24 33 8 160 8 laced true accel true rgba 8/0,8/0,8/0,0/0 endmode This bug is fixed in kernel-image-2.6.10-1-386, Version 2.6.10-4. It would be nice to have the fix in 2.6.8 too, which is supposed to ship with sarge. Mirko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292290: kernel-image-2.6.8-1-k7: XFS filesystem corruption: Input/output error
Hi,
This is a followup for Debian bug http://bugs.debian.org/292290.
Joost van Baal [EMAIL PROTECTED] - Wed, Jan 26, 2005:
`./lib/modules/2.6.10-1-k7/kernel/drivers/atm/zatm.ko': Unknown error 990
I've heard of one other victim of this problem with this kernel.
Wessel Dankers [EMAIL PROTECTED] - Thu, Jan 27, 2005:
I myself have been a victim of this too, so I thought I'd join in.
Well, me too.
- the kernel was Debian's 2.6.8;
- the filesystem in question was XFS;
- software raid1 (mirroring) was used.
XFS complained about corrupted in-memory structures in some of the cases.
However, it is very unlikely that all three machines have bad RAM, and
memtest86+ reports no problems.
I am also using Debian's kernel-image-2.6.8-2-686 in Version 2.6.8-13.
First of all, I'm using a PIV, so this aint K7 specific. I am NOT
using RAID 1 nor LVM, pure XFS.
This first corruption appeared with my mail/debian-project/ folder,
precisely on the tmp/ subdirectory. The second appeared today, on
the ./usr/share/doc/texmf/help/Catalogue/entries/romannum.html:
dpkg: error processing
/var/cache/apt/archives/tetex-doc_2.0.2c-6_all.deb (--unpack):
unable to stat
`./usr/share/doc/texmf/help/Catalogue/entries/romannum.html' (which I
was about to install): Unknown error 990
This is a really serious XFS problem it seems.
Trying to understand the problem suggested I tried stracing:
bee% LC_ALL=C strace -f ls debian-project-fucked/tmp 21
...
rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) =
0
brk(0) = 0x805b000
brk(0x807c000) = 0x807c000
brk(0) = 0x807c000
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=24, ws_col=80, ws_xpixel=644,
ws_ypixel=388}) = 0
stat64(debian-project-fucked/tmp, {st_mode=0, st_size=0, ...}) = -990
write(2, ls: , 4ls: ) = 4
write(2, debian-project-fucked/tmp, 25debian-project-fucked/tmp) = 25
write(2, : Unknown error 990, 19: Unknown error 990) = 19
write(2, \n, 1
) = 1
The problems seems to occur with the stat64() syscall, but I couldn't
find out what error 990 is supposed to be in the /usr/include headers
so I moved on to the kernel source and looked to the various syscalls
implementations. I also tried understanding what syscalls could
trigger the problem:
I checked with:
bee% LC_ALL=C strace zsh -e -c cd debian-project-fucked/tmp; ls
and got the error with a chdir() too, and hence looked at sys_chdir().
Then I checked whether this was directory specific, and tried:
bee% LC_ALL=C strace -f ls -i \
/usr/share/doc/texmf/help/Catalogue/entries/ 21
I got errors on a bunch of files, in the lstat64().
Then I looked upstream, first at bugme.osdl.org, and found:
http://bugme.osdl.org/show_bug.cgi?id=3224 (still open)
Finally, I looked at SGI's bugzilla, and found a first bug bubble:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=197
The problem also seems to appear in a comment of:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=383
197 is really worth reading, and using MD / LVM devices seems to help
trigger the bug.
These are dups of the above:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=204
http://oss.sgi.com/bugzilla/show_bug.cgi?id=207
The final patch attached to the bug report is:
http://oss.sgi.com/bugzilla/attachment.cgi?id=59action=view
I couldn't find an applied version in the kernel, it looked somehow too
much different but the xfs_finish_reclaim_all() was there...
2.6.8 was released in august 2004, and the patch mentionned dates
january 2003, so I can only think we face a different bug.
Then I went thoroughly through the bugzilla and found another bug which
might be related:
http://oss.sgi.com/bugzilla/show_bug.cgi?id=338 is on a 2.4 kernel
When I found out error 990 means EFSCORRUPTED, I thought I wouldn't be
able to track down the problem any further...
So I'm about to get a fresh xfsprogs or a live CD and xfs_repair my FS
to get a log and send it upstream.
Regards,
--
Loïc Minier [EMAIL PROTECTED]
Neutral President: I have no strong feelings one way or the other.
Bug#293481: kernel-image-2.6.8-2-686: Cannot open root device
Nigel Stephens wrote: Package: kernel-image-2.6.8-2-686 Version: 2.6.8-12 Severity: normal My current 2.6.6 kernel boots and runs OK on my Toshiba Tecra S1 laptop. But when I try to boot the 2.6.8 (or 2.6.10) kernel the bootstrap fails early on like this: RAMDISK: Loading 4540 blocks [1 disk] into ramdisk... done. VFS: Mounted root (cramfs filesystem) readonly. VFS: Cannot open root device hda5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) [snip] title Debian GNU/Linux, kernel 2.6.8-2-686 root(hd0,4) kernel /boot/vmlinuz-2.6.8-2-686 root=/dev/hda5 ro panic=60 initrd /boot/initrd.img-2.6.8-2-686 Looks like some driver went missing from this initrd. This would be a bug in initrd-tools (http://bugs.debian.org/initrd-tools). Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293508: initrd-tools refuses to make an initrd when lvm support is compiled, in the kernel
Package: initrd-tools Version: 0.1.77 I'm trying to switch from a 2.4.24 kernel to a 2.6.10 kernel and in the process go from lvm1 to lvm2. My root is also on lvm. When i compile a kernel with lvm2 in it, so no dm-mod to be found, mkinitrd refuses to build an initrd saying Kernel does not support LVM. If i set lvm2 as module, then it makes an initrd. [EMAIL PROTECTED] mkinitrd -o initrd.img-2.6.10.03feb2005-skas3-v7 -r /dev/main/lv_root 2.6.10.03feb2005-skas3-v7 /usr/sbin/mkinitrd: /dev/mapper/main-lv_root: Kernel does not support LVM [EMAIL PROTECTED] grep DM /boot/config-2.6.10.03feb2005-skas3-v7 ... CONFIG_BLK_DEV_DM=y ... I don't think it's related to bug #291386 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291386 as lvm1 is removed from my system ii lvm-common 1.5.17The Logical Volume Manager for Linux (common rc lvm10 1.0.8-8 The Logical Volume Manager for Linux ii lvm2 2.00.32-1 The Linux Logical Volume Manager ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel modules ii coreutils5.2.1-2The GNU core utilities ii fileutils 5.2.1-2 The GNU file management utilities (transitional package) Somebody on the debian-user list said the mkinitrd script probably has an error when checking for lvm2. It would be nice if this could be fixed. Regards, Benedict Verheyen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292601: kernel: Updated .glade files
On Thu, Feb 03, 2005 at 04:05:13PM +0100, Joachim Nilsson wrote: On Thu, Feb 03, 2005 at 11:20:42AM +0900, Horms wrote: On Mon, Jan 31, 2005 at 12:27:35PM +0100, Joachim Nilsson wrote: Mon 2005-01-31 at 13:30 +0300 Simon Horman wrote: On Fri, Jan 28, 2005 at 04:41:31PM +0100, Joachim Nilsson wrote: [1] - http://lists.debian.org/debian-kernel/2005/01/msg00171.html Is gconfig even maintained upstream? Dunno, but 2.6.10-ac5 has the following changelog entry that might be worth taking a closer look at: * Make gconfig work with current gtk 2.4 (J Magallon) That is interesting indeed. I have attached the associated patch. Could you take a moment to see if it resolves the problem as well as your patch does. The bk patch does solve the errors. It does this mainly by removing the use of custom icons for single|split|full view and replacing them with (imo badly chosen) stock icons. I.e., the patch focuses on solving the runtime errors, the annoying warnings remain. My patch otoh keep the original icons, the same as are used in the xconfig/kconfig toolbar. I do this with replace_button_icon(), which is a new function that replace missing icons from the .glade file. On top of that I also sneeked in a segfault fix on lines @@ -851,9 +851,12 @@ to grey out the back button in single mode. It is necessary to handle if the user changes from a deeply nested place in split mode to single mode and then presses back. I know I'm not exactly impartial here, but the bk patch is ugly. Maybe we should let our patch flow upstream? I think that would be an excellent idea. Perhaps you could try making a patch relative to what is currently upstream and send that to lkml and CC whoever signed off on the last patch. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293309: kernel-image-2.4.27-2-686: kernel-image fails unattended install
On Wed, Feb 02, 2005 at 10:25:43AM -0700, dann frazier wrote: On Wed, 2005-02-02 at 07:28 -0500, Alex Mohr wrote: Package: kernel-image-2.4.27-2-686 Severity: normal Unattended upgrades of kernel-image are difficult because the following message is generated without an obvious way of removing it. Perhaps it could detect when DEBCONF_FRONTEND is noninteractive and not display? Seems like this would best fit as an option in /etc/kernel-img.conf, and therefore should be reassigned to kernel-package. Yes, isn't that what the clobber_modules option does? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
