Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
On Wed, 16 Jul 2008 10:57:44 +0200 maximilian attems [EMAIL PROTECTED] wrote: On Tue, 15 Jul 2008, Daniel Dickinson wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490903 I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots sucessfully in that configuration with the megaraid. I suspect it is the SCSI-2 scanner as a non-RAID device on channel 2 that is confusing the megaraid_mbox driver. It worked with 2.6.24-1 though, so it is still a regression, just not as serious since it means I can't use my scanner, but can use my tape drive and channel 1 raid array. The scanner is connected with adaptors and cable that allow the SE SCSI-2 scanner to connect to the LVD Ultra-2 RAID controller (not custom stuff though) (with the controller configured for SCSI-2 Fast). can you try out 2.6.26 see trunk apt lines - http://wiki.debian.org/DebianKernel I tried the .26 kernel using the trunk apt shown with no luck. I still panics on boot, even with the scanner disconnected. There appears to be some difficulty with the interaction of the st tape driver and the megraid_mbox driver (assuming the problem isn't the st tape driver period, though I'd expect you'd already have more bug reports if that was the case, and the panic output on the screen says that the problem is in the megraid_mbox driver, though I can't see the entire panic due to it being larger than a single screen). Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org No more sea shells: Daniel's Webloghttp://cshore.wordpress.com signature.asc Description: PGP signature
Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
On Thu, Jul 31, 2008 at 02:27:10AM -0400, Daniel Dickinson wrote: On Wed, 16 Jul 2008 10:57:44 +0200 maximilian attems [EMAIL PROTECTED] wrote: On Tue, 15 Jul 2008, Daniel Dickinson wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490903 I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots sucessfully in that configuration with the megaraid. I suspect it is the SCSI-2 scanner as a non-RAID device on channel 2 that is confusing the megaraid_mbox driver. It worked with 2.6.24-1 though, so it is still a regression, just not as serious since it means I can't use my scanner, but can use my tape drive and channel 1 raid array. The scanner is connected with adaptors and cable that allow the SE SCSI-2 scanner to connect to the LVD Ultra-2 RAID controller (not custom stuff though) (with the controller configured for SCSI-2 Fast). can you try out 2.6.26 see trunk apt lines - http://wiki.debian.org/DebianKernel I tried the .26 kernel using the trunk apt shown with no luck. I still panics on boot, even with the scanner disconnected. There appears to be some difficulty with the interaction of the st tape driver and the megraid_mbox driver (assuming the problem isn't the st tape driver period, though I'd expect you'd already have more bug reports if that was the case, and the panic output on the screen says that the problem is in the megraid_mbox driver, though I can't see the entire panic due to it being larger than a single screen). could you please report upstream on bugzilla.kernel.org the debian kernel has no scsi specific patches. and let us know the upstream bug number. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
On Thu, 31 Jul 2008 09:26:52 +0200 maximilian attems [EMAIL PROTECTED] wrote: could you please report upstream on bugzilla.kernel.org the debian kernel has no scsi specific patches. and let us know the upstream bug number. Kernel Bugzilla #11194 -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org No more sea shells: Daniel's Webloghttp://cshore.wordpress.com signature.asc Description: PGP signature
Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
On Tue, 15 Jul 2008, Daniel Dickinson wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490903 I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots sucessfully in that configuration with the megaraid. I suspect it is the SCSI-2 scanner as a non-RAID device on channel 2 that is confusing the megaraid_mbox driver. It worked with 2.6.24-1 though, so it is still a regression, just not as serious since it means I can't use my scanner, but can use my tape drive and channel 1 raid array. The scanner is connected with adaptors and cable that allow the SE SCSI-2 scanner to connect to the LVD Ultra-2 RAID controller (not custom stuff though) (with the controller configured for SCSI-2 Fast). can you try out 2.6.26 see trunk apt lines - http://wiki.debian.org/DebianKernel thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490903 I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots sucessfully in that configuration with the megaraid. I suspect it is the SCSI-2 scanner as a non-RAID device on channel 2 that is confusing the megaraid_mbox driver. It worked with 2.6.24-1 though, so it is still a regression, just not as serious since it means I can't use my scanner, but can use my tape drive and channel 1 raid array. The scanner is connected with adaptors and cable that allow the SE SCSI-2 scanner to connect to the LVD Ultra-2 RAID controller (not custom stuff though) (with the controller configured for SCSI-2 Fast). -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 03:23:20 UTC 2008 ** Command line: root=/dev/mapper/Brennin-Root ro rootdelay=10 ** Not tainted ** Kernel log: [ 10.888197] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 10.888197] sdb: sdb1 [ 10.894878] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 11.379653] sd 2:0:0:0: [sdc] 7870464 512-byte hardware sectors (4030 MB) [ 11.386496] sd 2:0:0:0: [sdc] Write Protect is off [ 11.386496] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 11.386496] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 11.396434] sd 2:0:0:0: [sdc] 7870464 512-byte hardware sectors (4030 MB) [ 11.401293] sd 2:0:0:0: [sdc] Write Protect is off [ 11.401293] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 11.401293] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 11.401298] sdc: sdc1 [ 11.411373] sd 2:0:0:0: [sdc] Attached SCSI removable disk [ 15.882880] device-mapper: uevent: version 1.0.3 [ 15.885300] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] [ 35.433628] PM: Starting manual resume from disk [ 35.479727] EXT3-fs: INFO: recovery required on readonly filesystem. [ 35.479727] EXT3-fs: write access will be enabled during recovery. [ 35.489013] kjournald starting. Commit interval 5 seconds [ 35.489013] EXT3-fs: recovery complete. [ 35.510703] EXT3-fs: mounted filesystem with ordered data mode. [ 37.793889] udevd version 124 started [ 39.362024] Linux agpgart interface v0.103 [ 39.398057] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 39.435851] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 39.478260] agpgart: Detected an Intel 845G Chipset. [ 39.485786] agpgart: AGP aperture is 128M @ 0xf000 [ 39.590967] ACPI: PCI Interrupt :00:1f.3[B] - GSI 17 (level, low) - IRQ 17 [ 39.631742] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) [ 39.631895] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware [ 39.631966] iTCO_wdt: No card detected [ 39.668223] input: Power Button (FF) as /class/input/input1 [ 39.696295] ACPI: Power Button (FF) [PWRF] [ 39.696462] input: Power Button (CM) as /class/input/input2 [ 39.728300] ACPI: Power Button (CM) [PWRB] [ 39.932366] intel_rng: FWH not detected [ 41.193428] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005 [ 41.199192] usblp1: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3F17 [ 41.199301] usbcore: registered new interface driver usblp [ 41.638203] input: PC Speaker as /class/input/input3 [ 41.975523] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0 [ 41.975621] rtc0: alarms up to one month [ 42.241961] gameport: NS558 PnP Gameport is pnp00:10/gameport0, io 0x200, speed 774kHz [ 42.524894] input: ImPS/2 Logitech Wheel Mouse as /class/input/input4 [ 42.536707] ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 17 [ 42.536845] PCI: Setting latency timer of device :00:1f.5 to 64 [ 42.555706] parport_pc 00:09: reported by Plug and Play ACPI [ 42.555825] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 42.860415] intel8x0_measure_ac97_clock: measured 54912 usecs [ 42.860480] intel8x0: clocking to 48000 [ 43.039919] no PnP irq, using polling [ 48.545068] st0: Block limits 1 - 16777215 bytes. [ 49.385680] EXT3 FS on dm-1, internal journal [ 49.722337] loop: module loaded [ 50.020367] QEMU Accelerator Module version 1.3.0, Copyright (c) 2005-2007 Fabrice Bellard [ 50.020507] KQEMU installed, max_locked_mem=518140kB. [ 50.082655] tun: Universal TUN/TAP device driver, 1.6 [ 50.082655] tun: (C) 1999-2004 Max Krasnyansky [EMAIL PROTECTED] [ 50.151384] fuse init (API version 7.9) [ 50.250178] aufs 20080609 [ 53.985367] kjournald starting. Commit interval 5 seconds [ 53.994289] EXT3 FS on sda1, internal journal [ 53.994289] EXT3-fs: mounted filesystem with ordered data mode. [ 54.066703] kjournald starting. Commit interval 5 seconds [ 54.085339] EXT3 FS on dm-7, internal journal [ 54.085339] EXT3-fs:
