Bug#660446: linux-image-3.2.0-1-4kc-malta: Should include built-in support for ext4

2012-02-19 Thread Willi Mann
Package: linux-image-3.2.0-1-4kc-malta Version: 3.2.4-1 Severity: wishlist I've installed a mips system within qemu using the debian installer image for this architecture. Unfortunately the installer's default filesystem type ext4 is not built-in into the kernel image, which makes it very hard

Bug#590689: linux-2.6: Sudden slowdowns that feel like freezes in X

2011-08-30 Thread Willi Mann
Hi! On 2011-08-30 07:14, Jonathan Nieder wrote: Neat. Did this problem eventually go away, or do you still experience it? If the former, what's the oldest fixed version you remember (/var/log/dpkg.log* can help)? Unfortunately, I do not remember when this problem went away, but it is gone.

Bug#608698: linux-image-2.6.37-rc7-686: suspend/hibernate fails with pnp_bus_suspend+0x0/0x57 returns -5

2011-01-25 Thread Willi Mann
If you don't use the parallel port, you may be able to work around this by blacklisting the 'parport_pc' module. That seems to help, but it might just be hidden by another problem I'm facing after a few hibernate cycles: Colors of fonts change (mostly white to black), and the screen gets

Bug#608698: linux-image-2.6.37-rc7-686: suspend/hibernate fails with pnp_bus_suspend+0x0/0x57 returns -5

2011-01-02 Thread Willi Mann
Package: linux-2.6 Version: 2.6.37~rc7-1~experimental.1 Severity: normal After a few hibernate cycles, I can no longer suspend/hibernate my thinkpad T500. It fails with mentioned error - see the attached logs. Additionally, my external cherry USB keyboard (plugged in the Docking Station)

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

2010-10-11 Thread Willi Mann
it could very well be fixed in rc6 please test that first, thanks. Yes, it seems so. At least I could not reproduce it with rc6. WM -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

2010-10-06 Thread Willi Mann
Package: linux-2.6 Version: 2.6.36~rc5-1~experimental.1 Severity: important When trying to open a mail with with large images (e.g. 3 images with 4368x2912) in icedove the screen freezes and after a few seconds, a beep occurs (this is probably the kerneloops daemon) and the following messages

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

2010-10-06 Thread Willi Mann
Am 2010-10-06 13:11, schrieb maximilian attems: it could very well be fixed in rc6 please test that first, thanks. Hi! Is the i386 version of rc6 already somewhere available? The offical ones are currently waiting in NEW. thanks WM -- To UNSUBSCRIBE, email to

Bug#584259: initramfs-tools: breaks software suspend (hibernation)

2010-06-20 Thread Willi Mann
Am 2010-06-20 18:10, schrieb Ben Hutchings: On Sat, 2010-06-19 at 19:06 +0200, Willi Mann wrote: Hi! The problem can be traced to module hid_cherry. If it exists in the initrd, the resume works, otherwise it doesn't. This seems to indicate that hid_cherry doesn't fully reinitialise

Bug#584259: initramfs-tools: breaks software suspend (hibernation)

2010-06-19 Thread Willi Mann
Hi! The problem can be traced to module hid_cherry. If it exists in the initrd, the resume works, otherwise it doesn't. WM -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#584259: initramfs-tools: breaks software suspend (hibernation)

2010-06-09 Thread Willi Mann
Hi! -- resume # RESUME=/dev/sda6 RESUME='LABEL=amdlinux-swap' Does it work with 'RESUME=/dev/disk/by-label/amdlinux-swap'? No. If it still does not work then: can you please extract the broken and the working initramfs[1] and check the difference between them? Especially the included

Bug#584784: also applies to unstable

2010-06-07 Thread Willi Mann
Am 2010-06-07 03:44, schrieb Ben Hutchings: On Sun, 2010-06-06 at 23:18 +0200, Willi Mann wrote: Kernel panic - not syncing: To avoid data corruption io_map_base MUST be set with multiple PCI domains. has been applied on all PCI MIPS systems since Linux 2.6.24. Are you quite sure

Bug#584784: /boot/vmlinux-2.6.34-1-4kc-malta: no longer boots in qemu

2010-06-06 Thread Willi Mann
Package: linux-2.6 Version: 2.6.34-1~experimental.1 Severity: grave File: /boot/vmlinux-2.6.34-1-4kc-malta This kernel no longer boots in qemu 0.12.4+dfsg-1 (boot messages attached). The last version that successfully booted is 2.6.32-9. I haven't yet tested the current unstable kernel. --

Bug#584784: also applies to unstable

2010-06-06 Thread Willi Mann
found 584784 2.6.32-15 thanks Hi! Unfortunately, this bug also applies to unstable, only current testing kernel is unaffected. WM -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#584259: initramfs-tools: breaks software suspend (hibernation)

2010-06-02 Thread Willi Mann
Package: initramfs-tools Version: 0.95.1 Severity: important Since the upgrade to 0.94.4 in testing, software suspend's resume does not complete. The screen it ends up with is black except a blinking cursor, but I can use Alt+F1 to switch to a screen that shows some messages concerning

Bug#516018: linux-image-2.6.26-1-686: System shutdown fails (no poweroff)

2009-02-18 Thread Willi Mann
Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal I'm reporting this bug from a different machine than the machine the problem appears on, so I deleted the system information. When I hit the powerbutton, or choose shutdown from the kdm menu which I configured to invoke

Bug#516018: Clarification

2009-02-18 Thread Willi Mann
I meant the computer does *not* complete the system shutdown. And that applies to only about half of all system shutdowns, so it is not a stable bug. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#430776: linux-image-2.6.21-2-686: hangs on boot for 60 seconds while trying something related to pcmcia

2007-06-27 Thread Willi Mann
Package: linux-image-2.6.21-2-686 Severity: normal This bug is a regression from linux-image-2.6.18-4-686 2.6.18.dfsg.1-12 The messages before the hang are: Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06 pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff cs: IO port

Bug#430779: linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected.

2007-06-27 Thread Willi Mann
Package: linux-image-2.6.21-2-686 Severity: important This bug is a regression from linux-image-2.6.18-4-686 2.6.18.dfsg.1-1 When booted with 2.6.21, the mouse pointer moves with an unacceptable delay. Sound played with xmms has interrupts, and even now, while typing this report on the

Bug#430779: linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected.

2007-06-27 Thread Willi Mann
userspace cpufreqd are mostly useless, use ondemand echo ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor That was the first thing I did after I found out that it's a little bit better (the sound was a little bit less crippled) without any cpu frequency scaling. But

Bug#430779: linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected.

2007-06-27 Thread Willi Mann
dmesg output and lsmod output attached. Note the lines PCI: Transparent bridge - :00:1e.0 PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Please report the result to linux-kernel to fix this permanently PCI: Bus #07 (-#0a) is hidden behind

Bug#430779: linux-image-2.6.21-2-686: System seems to have microhangs, especially the mouse and sound are affected.

2007-06-27 Thread Willi Mann
Are these bugs related to this lines? Willi yes maybe, do what they say, but before try really latest, see trunk http://wiki.debian.org/DebianKernel The bad news: These lines did not go away. the good news: The issue described in this bug report went away, and the whole system even feels

Re: svn /patch-tracking/

2006-08-02 Thread Willi Mann
I've found http://svn.debian.org/wsvn/kernel/patch-tracking/ a really useful way of knowing what the kernel team thinks about kernel vulnerabilities. But it seems to have gone away. Has it moved somewhere else, or is there a better way for me to check debians position against

Bug#314954: fixed in 2.6.16-git16

2006-03-29 Thread Willi Mann
Hi! This bug is fixed in 2.6.16-git16, commit aef4e266964bc15861b5835c1f5b9d2ebc155c2a Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

linux-doc-* Package

2006-01-23 Thread Willi Mann
Hi! Why was the linux-doc-* package removed? Is that a bug or was it removed deliberately? I cannot find anything matching linux-doc in the changelog since 2.6.14, that's why I am asking. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-30 Thread Willi Mann
I've tried; it wasn't accepted. The patch below should be more acceptable to the maintainer. Try it instead of the other one; it ought to get rid of all those error messages showing up in the log as well as fixing the mouse problem. That is, it won't prevent the actual errors from occurring

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-22 Thread Willi Mann
I've dropped Helmut Zeisel as cc: and will send him notice a when the issue is resolved. He can read our conversation in the mailing list archive anyway. I've tried; it wasn't accepted. The patch below should be more acceptable to the maintainer. Try it instead of the other one; it ought to

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-21 Thread Willi Mann
That particular error generally means that something is interfering with the USB data transmission. It could be a poor cable connection, or it could be the mouse sending a bad signal, or it could be some sort of outside electromagnetic interference. I would like to test with other USB

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-17 Thread Willi Mann
Yes. Read Documentation/usb/usbmon.txt in the kernel source. Ok, here is what I did: cat 2t - minimize the gnome-terminal - surfed the web - suddenly mouse died - Strg + Alt + F1, Alt+ F7 - reopened the terminal - marked the last 200 lines - pasted in file - grepped for the mouse identifier

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-17 Thread Willi Mann
Yes indeed. This looks very similar to the problem reported in http://bugzilla.kernel.org/show_bug.cgi?id=4916 See especially comment #19. It's possible that the patch adding an HID reset routine (the last attachment in the bug report) will work for you. You might have to fiddle with it

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-17 Thread Willi Mann
I now recreated the patch in a more usable way. BTW: Dec 17 20:50:30 wmiwilli kernel: mtrr: 0xe800,0x800 overlaps existing 0xe800,0x100 Dec 17 21:01:25 wmiwilli kernel: drivers/usb/input/hid-core.c: input irq status -84 received Dec 17 21:25:43 wmiwilli kernel:

Bug#314954: [Linux-usb-users] Re: logitech usb mouse dies

2005-12-04 Thread Willi Mann
To get more information, turn on USB verbose debugging (CONFIG_USB_DEBUG) in the kernel configuration and rebuild the USB drivers. Post the kernel or dmesg log showing what happens when the connection is lost. I've used the debian source for that. They currently don't patch anything

Re: added memory protection from kernel 2.6.11 -- 2.6.12 ?

2005-12-04 Thread Willi Mann
I was wondering if the current kernels (=2.6.12) have some kind of additional memory protection addded. Specifically, I'm trying to read from the process memory of another process (using gdb) which works just fine on kernel version up to (and including) 2.6.11. (This is inevitable for me since

Bug#314954: logitech usb mouse dies

2005-12-01 Thread Willi Mann
I have already reported this bug in the Debian BTS with many details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314954 I have now tested with a second logitech mouse attached. Bus 004 Device 004: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 TetraHub Bus 004 Device

Bug#295627: seems fixed

2005-11-19 Thread Willi Mann
It seems this bug is fixed: (linux-2.6.12 is from kernel.org) $ grep usp -A4 -B4 linux-2.6.12/include/asm-sparc64/compat.h static __inline__ void __user *compat_alloc_user_space(long len) { struct pt_regs *regs = current_thread_info()-kregs; unsigned long usp =

Bug#314954: bug still reproduceable

2005-11-18 Thread Willi Mann
Hi! I can still reproduce this bug. The strange thing is: sometimes it happens very often, sometimes I have no problems for several hours. I have now disabled gpm, and since then, the workaround without unplugging the mouse is reduced to Strg + Alt + F1, Alt + F7. So it seems the mouse

Note about unfortunate message from linux-image

2005-11-15 Thread Willi Mann
Hi! I'm not reporting this as bug, because I think I've read this is fixed in the kernel-package in experimental anyway. Just in case it's not fixed... The bug is that linux-image complains about a possible previous install of the kernel, probably just because the linux-headers that were

Bug#337045: race condition?: sometimes fails to correctly detect my harddisk

2005-11-04 Thread Willi Mann
I've seen similar symptoms (missing devices at boot) go away when I've increased the delay after the call to udevsynthesize in the initrd's init. You can try increasing the argument to sleep in /usr/share/initramfs-tools/init (around line 72): # Populate /dev tree log_begin_msg Initializing

Re: Bug#337045: linux-image-2.6.14-1-686: race condition?: sometimes fails to correctly detect my harddisk

2005-11-03 Thread Willi Mann
hda: , ATA disk drive .. ide0: I/O ressource 0x3F6 - 0x3F6 not free hda: Error, ports already in use ide0 at 0x1f0-0x1f7, 0x3f6 in irq 14 Sorry for the incomplete report, I have no idea where I could save the dmesg output the next time. Ok, today I got the same problem again,

Bug#333003: linux-image-2.6.14-1-686: vesafb is missing on video/drivers modules

2005-11-02 Thread Willi Mann
[resend, it was accidently sent to @lists.debian.org instead of @bugs.debian.org] It was suggested to me by Sven Luther, that as vesafb is now compiled into the kernel, it would make sense to do the same with fbcon. Can anyone comment on this idea? It sounds like it would solve most of the

Bug#337045: linux-image-2.6.14-1-686: race condition?: sometimes fails to correctly detect my harddisk

2005-11-02 Thread Willi Mann
Package: linux-image-2.6.14-1-686 Version: 2.6.14-2 Severity: important First try: I got the following messages during boot (I noted them on paper, so there might be some mistakes) hda: , ATA disk drive .. ide0: I/O ressource 0x3F6 - 0x3F6 not free hda: Error, ports already in use

Bug#337045: linux-image-2.6.14-1-686: I hate to me too, but me too

2005-11-02 Thread Willi Mann
One thing I did do directly before this error is try and remove tg3 and replace with the non-free bcm5700 network card driver (the reboot was supposed to finish the replacement, until I realised the initramfs is loading all my modules now- which is a different bag of fun for a different bug

Re: Bug#333003: linux-image-2.6.14-1-686: vesafb is missing on video/drivers modules

2005-11-01 Thread Willi Mann
Some more info: there's no error message, the kernel output behaves as vesafb would work. (vga=0x305) $ egrep -i 'vesa|fb' /var/log/messages | cut -b 26- kernel: vesafb: framebuffer at 0xe800, mapped to 0xde88, using 1536k, total 32576k kernel: vesafb: mode is 1024x768x8,

what happened to vesafb support in 2.6.13-1?

2005-10-09 Thread Willi Mann
Hi! Can someone please tell me what happened to vesafb support in 2.6.13-1? (CONFIG_FB_VESA=m in 2.6.12-10 vs. not set in 2.6.13-1) I get a blank screen when booting with vga=791. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Re: what happened to vesafb support in 2.6.13-1?

2005-10-09 Thread Willi Mann
the old legacy modular vesafb patch got dropped. and it seems it was overlooked to set them to yes. thanks for the quick response. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#314954: gpm restart as solution

2005-08-16 Thread Willi Mann
thanks for your feedback. tg3 is again included in 2.6.12 due to relicensing of the firmware. please try that linux image. As I have already written in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314954;msg=27 , this bug still occurs, but only very seldomly. I think it occured only

Bug#314954: gpm restart as solution

2005-06-20 Thread Willi Mann
gpm restart as solution only helps in case I switch to the console. Restarting gpm from an x terminal does not help. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]