Re: kernel BUG at ide-cd.c:1726 in 2.6.24-03863-g0ba6c33 && -g8561b089

spin_unlock_irqrestore(&ide_lock, flags); > Fixes the crash on boot for me ... Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin signature.asc Description: Digital signature

Re: [2.6.24] bcm203x bluetooth dongle does not work

Bluetooth: Broadcom Blutonium firmware driver ver 1.1 usbcore: registered new interface driver bcm203x bcm203x_complete: URB failed with status -84 usb 1-1: USB disconnect, address 2 Flo -- Florian Lohoff [

Re: [2.6.24] bcm203x bluetooth dongle does not work

> kernels 2.6.19-2.6.23 are working. We might have missed a change inside > the USB subsystem within the 2.6.24 timeframe. My tests were on 2.6.24 which does not work as described. Newer kernels dont boot due to crash in ide-cd so i cant test ... Flo -- Florian Lohoff [

[2.6.24] bcm203x bluetooth dongle does not work

. It still applies and fixes my problem: Ubuntu Bug: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85247 Patch: http://launchpadlibrarian.net/7058766/bcm203x-2.6.20-backport.diff So it seems this patch never went in but most likely should. Flo -- Florian

Re: kernel BUG at ide-cd.c:1726 in 2.6.24-03863-g0ba6c33 && -g8561b089

e8 81 6d 32 e0 31 c9 31 d2 89 c3 8b 45 d8 e8 bf 1e 17 e0 85 c0 74 04 <0f> 0b eb fe 8b 47 2c 89 da 8b 40 08 c7 40 1c 00 00 00 00 b8 80 [ 40.410255] EIP: [] cdrom_newpc_intr+0xfb/0x29f [ide_cd] SS:ESP 0068:de52bd8c [ 40.410255] Kernel panic - not syncing: Fatal exception in

Re: BUG: scheduling while atomic: ifconfig/0x00000002/4170

d wait_for_completion()'s > might_sleep() clearly didn't trigger earlier because Florian must've > had CONFIG_DEBUG_SPINLOCK_SLEEP off in his .config ... # CONFIG_DEBUG_SPINLOCK_SLEEP is not set Exactly ... Flo -- Florian Lohoff [EMAIL PROTECTED]

BUG: scheduling while atomic: ifconfig/0x00000002/4170

[ 382.529174] [] sock_ioctl+0x0/0x1be [ 382.529187] [] do_ioctl+0x1f/0x62 [ 382.529201] [] vfs_ioctl+0x237/0x249 [ 382.529211] [] do_sys_open+0xbb/0xc5 [ 382.529224] [] sys_ioctl+0x33/0x4d [ 382.529235] [] sysenter_past_esp+0x5f/0x85 [ 382.529253] === [ 382.530962

Re: 2.6.23-rc1 sky2 boot crash in sky2_mac_intr

gure out what is causing this crash and then use > git-bisect? Are there so many changes between 2.6.22-rc5 and 2.6.23-rc1 for the sky2? As the crash is not that reproducible, just occasionally on boot i guess bisecting is more or less waste of time. Flo -- Florian Lohoff [

Re: 2.6.23-rc1 sky2 boot crash in sky2_mac_intr

; hardware for testing. I'll try the above and keep you posted. The crash itself seems to be a 2.6.23-rc1 regression though. I never experienced this with 2.6.22-rc5 which i was running before. Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134

2.6.23-rc1 sky2 boot crash in sky2_mac_intr

1713] Kernel panic - not syncing: Fatal exception in interrupt Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin signature.asc Descript

Re: Linux, tcpdump and vlan

in use. As i was tracing dot1qinq i could actually see that only the outer vlan tag was beeing dropped. Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neit

Re: [6/6] 2.6.21-rc3: known regressions

7;s also be a probably related "doesn't boot" > problem. > My first guess would be commit 6bb74df481223731af6c7e0ff3adb31f6442cfcd > "clocksource init adjustments (fix bug #7426)". > > Jiri, is the message also present with 2.6.21-rc2 (at a different place

Boot fails with 2.6.20-rc3 / git-current Was: 2.6.20-rc3: Clocksource tsc unstable

est tm2 xtpr bogomips: 3657.63 clflush size : 64 -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin signature.asc Description: Digital signature

2.6.20-rc4 sky2 unsupported chip type 0xff / phy write timeout

Hi, i have random problems after fresh boot with the onboard sky2 on an Fujitsu Siemens Lifebook E8110. With 2.6.18-686-3 from the Debian repository i see random crashes on boot - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404107 With a Linux machine 2.6.20-rc4 #0 SMP PREEMP

[OOps] 2.6.11-rc3 rmmod ide-scsi

6b 34 02 8b 43 1c 89 44 24 -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Heisenberg may have been here. pgpRHRt4MHkWV.pgp Description: PGP signature

Re: kernel BUG at fs/sysfs/symlink.c:87

On Mon, Jan 24, 2005 at 04:51:00PM +0100, Florian Lohoff wrote: > Hi, > while using the bridging code between a tap0 and a real eth1 i got this: > > Linux zmgr1.wstk.mediaways.net 2.6.10-zmgr-p3cel #1 Mon Jan 24 16:15:39 CET > 2005 i686 GNU/Linux > > UP, P3 Celeron, Non-Pr

Re: kernel BUG at fs/sysfs/symlink.c:87

not too familiar with that code. Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Heisenberg may have been here. pgpNnW71xhTsP.pgp Description: PGP signature

kernel BUG at fs/sysfs/symlink.c:87

44 24 04 8b 40 30 89 44 24 04 <7>tap0: no IPv6 routers present Flo -- Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 Heisenberg may have been here. pgpAyriBLhf6U.pgp Description: PGP signature

Re: Oops in iput

es are 100% bug free, but I wouldn't > consider them as the prime suspect for an oops that happened elsewhere > either. It could be hw or any other part of kernel just as well... What > about memtest86? I'll try Flo -- Florian Lohoff [EMAIL PROTECTED]

Oops in iput

lt;_EIP+0x10> c0133cb7 Code; c0133cb5 e: 89 c3 mov%eax,%ebx Code; c0133cb7 10: 85 db test %ebx,%ebx Code; c0133cb9 12: 74 10 je 24 <_EIP+0x24> c0133ccb 1 warning issued. Results may not be reliable. -- Florian

Serial console != baud 9k6

serial console from the arch specific stuff with something else than the default baud rate ? Flo -- Florian Lohoff [EMAIL PROTECTED] +49-5201-669912 Why is it called "common sense" when nobody seems to have any? - To unsubscribe from this list: se

Re: [Linux-IrDA]Re: [IrDA+SMP] Lockup in handle_IRQ_event

disables IRQs on the local CPU so a different CPU could easily stumple half way as this is definitly non atomic. Or is the tty layer protected by some "big tty lock" ? Flo -- Florian Lohoff [EMAIL PROTECTED] +49-5201-669912 Why is it called "commo

[OOPS] 2.2.17 free_wait+49/116 / possible memory corruption ?

0 addl $0x0,(%eax) 1 error issued. Results may not be reliable. Other suspicions ? Flo -- Florian Lohoff [EMAIL PROTECTED] +49-5201-669912 "Write only memory - Oops. Time for my medication again ..." - To unsubscribe from this list: sen

get_tty_baud_rate() on sparc64

uot; issue ? Flo -- Florian Lohoff [EMAIL PROTECTED] +49-5201-669912 "Write only memory - Oops. Time for my medication again ..." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTE

ioremap & Co i386 -> sparc64

EM_MASK, AA_CHIP_PCI_SIZE); While resetting the first writeb (ba contains cd1865_base) [...] /* Set GSVR to 0x0 */ writeb(0x00, ba + CD1865_GSVR); This is all Kernel 2.2.17 Flo -- Florian Lohoff [EMAIL PROTECTED] +49-5201-669912 &quo

2.2.17 doesnt build on sparc64 with CONFIG_IP_PNP

etup.c:553: for each function it appears in.) make[2]: *** [setup.o] Error 1 make[2]: Leaving directory `/usr/src/linux/arch/sparc64/kernel' make[1]: *** [_dir_arch/sparc64/kernel] Error 2 make[1]: Leaving directory `/usr/src/linux' make: *** [stamp-build] Error 2 Flo -- Florian Lohoff