Bug#769135: linux-image-3.2.0-4-amd64: Backport of fix for JMicron USB->SATA bridges

2014-11-11 Thread Michael Büsch
0 +0200 @@ -1916,6 +1916,13 @@ USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_IGNORE_RESIDUE ), +/* Reported by Michael Büsch */ +UNUSUAL_DEV( 0x152d, 0x0567, 0x0114, 0x0114, + "JMicron", + "USB to ATA/ATAPI Bridge", + USB_SC_DEVICE, USB_PR_DEVICE, NULL, + US_FL_BR

Bug#655242: ext4: Warning at ext4 inode.c:885

2012-01-09 Thread Michael Büsch
On Mon, 09 Jan 2012 18:34:32 +0100 Michael Buesch wrote: > The ext4 filesystem in question is the rootfs on a LUKS encrypted partition. > The machine had at least one s2disk (uswsusp) cycle before this happened. But > this probably doesn't matter. Just for completeness. Hm, now that I think abo

Bug#588196: b43: does not join multicast groups

2010-07-15 Thread Michael Büsch
On 07/15/2010 10:51 AM, Simon Richter wrote: The same applies to receiving. The RX queue is also dropped on switch from DMA to PIO. Sure, but the packet is repeated every ten seconds. The problem is that none of those packets is received, even long after the switch to PIO. The filter flags ar

Bug#588196: b43: does not join multicast groups

2010-07-14 Thread Michael Büsch
On 07/14/2010 09:50 AM, Simon Richter wrote: Hi, On Tue, Jul 13, 2010 at 04:05:10PM +0200, Michael Büsch wrote: So it is up to the upper layer to detect the failure. I don't think it's possible to automatically detect such incidents for multicast transmissions. So the mechanism

Bug#588196: b43: does not join multicast groups

2010-07-13 Thread Michael Büsch
On 07/13/2010 03:06 PM, Simon Richter wrote: Hi, On Tue, Jul 13, 2010 at 03:00:00PM +0200, Michael Büsch wrote: But I wanna say again that this all is expected behavior. The PIO fallback workaround randomly drops packets when switching modes. So it is expected that certain handshaking

Bug#588196: b43: does not join multicast groups

2010-07-13 Thread Michael Büsch
On 07/13/2010 09:37 AM, Simon Richter wrote: That appears to work, at least I have v6 addresses now. Unlike before, you now have communication. Well, v4 worked fine before. :) That's very nice. But I wanna say again that this all is expected behavior. The PIO fallback workaround randomly drop