Bug#504138: linux-image-2.6.26-1-686: Framebuffer goes blank after X start

[Apelete Seketeli]

Package: linux-image-2.6.26-1-686
Version: 2.6.26-9
Severity: normal

After starting X server all tty framebuffers go blank. Before X start,
framebuffer display boot process normally
though. It seems vesafb kernel module is not loaded at boot, resulting
in the blank framebuffers.
The problem does not appear in version 2.6.26.8.


-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-9) ([EMAIL PROTECTED]) (gcc
version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Oct
18 16:22:25 UTC 2008

** Command line:
root=/dev/sda5 ro quiet vga=792 splash acpi_sleep=s3_bios

** Not tainted

** Kernel log:
[   68.894667] PM: Writing back config space on device :03:00.0 at
offset 1 (was 100102, writing 100106)
[   68.894667] firmware: requesting iwlwifi-3945-1.ucode
[   69.033278] Registered led device: iwl-phy0:radio
[   69.033278] Registered led device: iwl-phy0:assoc
[   69.033278] Registered led device: iwl-phy0:RX
[   69.033278] Registered led device: iwl-phy0:TX
[   71.193352] NET: Registered protocol family 10
[   71.193352] lo: Disabled Privacy Extensions
[   71.193352] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   71.193352] ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready
[   72.354378] CPU0 attaching NULL sched-domain.
[   72.354378] CPU1 attaching NULL sched-domain.
[   72.357935] CPU0 attaching sched-domain:
[   72.357944]  domain 0: span 0-1
[   72.357948]   groups: 0 1
[   72.357956]   domain 1: span 0-1
[   72.357960]groups: 0-1
[   72.357966] CPU1 attaching sched-domain:
[   72.357970]  domain 0: span 0-1
[   72.357974]   groups: 1 0
[   72.357980]   domain 1: span 0-1
[   72.357984]groups: 0-1
[  248.682451] CPU0 attaching NULL sched-domain.
[  248.682451] CPU1 attaching NULL sched-domain.
[  248.688228] CPU0 attaching sched-domain:
[  248.688234]  domain 0: span 0-1
[  248.688237]   groups: 0 1
[  248.688247] CPU1 attaching sched-domain:
[  248.688251]  domain 0: span 0-1
[  248.688256]   groups: 1 0
[  253.616093] wlan0_rename: Initial auth_alg=0
[  253.616100] wlan0_rename: authenticate with AP 00:10:c6:f2:4f:e5
[  253.618879] wlan0_rename: RX authentication from 00:10:c6:f2:4f:e5
(alg=0 transaction=2 status=0)
[  253.618885] wlan0_rename: authenticated
[  253.61] wlan0_rename: associate with AP 00:10:c6:f2:4f:e5
[  253.623222] wlan0_rename: RX AssocResp from 00:10:c6:f2:4f:e5
(capab=0x411 status=0 aid=1)
[  253.623227] wlan0_rename: associated
[  253.623237] wlan0_rename: switched to short barker preamble
(BSSID=00:10:c6:f2:4f:e5)
[  253.630740] ADDRCONF(NETDEV_CHANGE): wlan0_rename: link becomes ready
[  269.011180] wlan0_rename: no IPv6 routers present
[  651.686769] CE: hpet increasing min_delta_ns to 15000 nsec
[ 3224.843319] CPU0 attaching NULL sched-domain.
[ 3224.843319] CPU1 attaching NULL sched-domain.
[ 3224.847343] CPU0 attaching sched-domain:
[ 3224.847352]  domain 0: span 0-1
[ 3224.847356]   groups: 0 1
[ 3224.847363]   domain 1: span 0-1
[ 3224.847367]groups: 0-1
[ 3224.847373] CPU1 attaching sched-domain:
[ 3224.847377]  domain 0: span 0-1
[ 3224.847381]   groups: 1 0
[ 3224.847387]   domain 1: span 0-1
[ 3224.847391]groups: 0-1
[ 3229.368885] wlan0_rename: No ProbeResp from current AP
00:10:c6:f2:4f:e5 - assume out of range
[ 3229.728578] CPU0 attaching NULL sched-domain.
[ 3229.728585] CPU1 attaching NULL sched-domain.
[ 3229.732521] CPU0 attaching sched-domain:
[ 3229.732521]  domain 0: span 0-1
[ 3229.732521]   groups: 0 1
[ 3229.732521] CPU1 attaching sched-domain:
[ 3229.732521]  domain 0: span 0-1
[ 3229.732521]   groups: 1 0
[ 3231.043710] CPU0 attaching NULL sched-domain.
[ 3231.043719] CPU1 attaching NULL sched-domain.
[ 3231.065746] CPU0 attaching sched-domain:
[ 3231.065746]  domain 0: span 0-1
[ 3231.065746]   groups: 0 1
[ 3231.065746]   domain 1: span 0-1
[ 3231.065746]groups: 0-1
[ 3231.065746] CPU1 attaching sched-domain:
[ 3231.065746]  domain 0: span 0-1
[ 3231.065746]   groups: 1 0
[ 3231.065746]   domain 1: span 0-1
[ 3231.065746]groups: 0-1
[ 3239.628956] ACPI: PCI interrupt for device :03:00.0 disabled
[ 3239.630312] ACPI: PCI Interrupt :03:00.0[A] -> GSI 17 (level,
low) -> IRQ 17
[ 3239.630486] PM: Writing back config space on device :03:00.0 at
offset 1 (was 100102, writing 100106)
[ 3239.674448] Registered led device: iwl-phy0:radio
[ 3239.674448] Registered led device: iwl-phy0:assoc
[ 3239.674448] Registered led device: iwl-phy0:RX
[ 3239.674448] Registered led device: iwl-phy0:TX
[ 3239.675916] ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready
[ 3242.389676] CPU0 attaching NULL sched-domain.
[ 3242.389684] CPU1 attaching NULL sched-domain.
[ 3242.393751] CPU0 attaching sched-domain:
[ 3242.393751]  domain 0: span 0-1
[ 3242.393751]   groups: 0 1
[ 3242.393751] CPU1 attaching sched-domain:
[ 3242.393751]  domain 0: span 0-1
[ 3242.393751]   groups: 1 0
[ 3341.151693] wlan0_rename: Initial auth_alg=0
[ 3341.151693] wlan0_rename: authenticate with AP 00:10:c6:f2:4f:e

Bug#419950: tulip eth driver init

[Lou Poppler]

On Thu, 30 Oct 2008, Paul Medynski wrote:


Hi Lou,

I'm experiencing the same problem that you outlined in the email I found 
below.  I noticed that we have the same ADMtek ethernet card.  Here's my 
dmesg showing the ide and eth0 initialization intermingled:


[3.492758] Uniform Multi-Platform E-IDE driver
[3.492837] ide: Assuming 33MHz system bus speed for PIO modes; override 
with idebus=xx
[3.517233] VP_IDE: IDE controller (0x1106:0x0571 rev 0x10) at  PCI slot 
:00:07.1

[3.517352] VP_IDE: not 100% native mode: will probe irqs later
[3.517454] VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on 
pci:00:07.1

[3.517540] ide0: BM-DMA at 0xd000-0xd007
[3.517608] ide1: BM-DMA at 0xd008-0xd00f
[3.517669] Probing IDE interface ide0...
[3.685949] usbcore: registered new interface driver usbfs
[3.686096] usbcore: registered new interface driver hub
[3.686250] usbcore: registered new device driver usb
[3.707389] USB Universal Host Controller Interface driver v3.0
[3.892502] Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
[3.972184] hda: WDC WD2500JB-00REA0, ATA DISK drive
[4.032028] Marking TSC unstable due to: TSC halts in idle.
[4.255177] hdb: WDC WD3200AAJB-00WGA0, ATA DISK drive
[4.310938] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[4.311035] hda: UDMA/66 mode selected
[4.311167] hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[4.311255] hdb: UDMA/66 mode selected
[4.311394] Probing IDE interface ide1...
[4.724888] hdc: WDC WD2500JB-00REA0, ATA DISK drive
[5.004149] hdd: WDC WD2000JB-00GVC0, ATA DISK drive
[5.060137] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[5.060225] hdc: UDMA/66 mode selected
[5.060356] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[5.061590] hdd: UDMA/66 mode selected
[5.062912] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[5.063060] ide1 at 0x170-0x177,0x376 on irq 15
[5.064740] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
[5.064811] PCI: setting IRQ 12 as level-triggered
[5.064821] ACPI: PCI Interrupt :00:07.2[D] -> Link [LNKD] -> GSI 12 
(level, low) -> IRQ 12

[5.064992] uhci_hcd :00:07.2: UHCI Host Controller
[5.065287] uhci_hcd :00:07.2: new USB bus registered, assigned bus 
number 1

[5.065396] uhci_hcd :00:07.2: irq 12, io base 0xd400
[5.065708] usb usb1: configuration #1 chosen from 1 choice
[5.065859] hub 1-0:1.0: USB hub found
[5.065936] hub 1-0:1.0: 2 ports detected
[5.168344] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[5.168423] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[5.168496] usb usb1: Product: UHCI Host Controller
[5.168557] usb usb1: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
[5.168620] usb usb1: SerialNumber: :00:07.2
[5.168876] ACPI: PCI Interrupt :00:07.3[D] -> Link [LNKD] -> GSI 12 
(level, low) -> IRQ 12

[5.169052] uhci_hcd :00:07.3: UHCI Host Controller
[5.169178] uhci_hcd :00:07.3: new USB bus registered, assigned bus 
number 2

[5.169286] uhci_hcd :00:07.3: irq 12, io base 0xd800
[5.169594] usb usb2: configuration #1 chosen from 1 choice
[5.169735] hub 2-0:1.0: USB hub found
[5.169812] hub 2-0:1.0: 2 ports detected
[5.176864] No dock devices found.
[5.215964] SCSI subsystem initialized
[5.261595] libata version 3.00 loaded.
[5.272409] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[5.272492] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[5.272566] usb usb2: Product: UHCI Host Controller
[5.272625] usb usb2: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
[5.272688] usb usb2: SerialNumber: :00:07.3
[5.274802] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[5.274879] PCI: setting IRQ 11 as level-triggered
[5.274889] ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKC] -> GSI 11 
(level, low) -> IRQ 11
[5.275399] tulip0:  MII transceiver #1 config 1000 status 7869 
advertising 05e1.
[5.279455] eth0: ADMtek Comet rev 17 at Port 0xe800, 00:04:5a:7c:4e:05, 
IRQ 11.

[5.383698] hda: max request size: 512KiB
[5.399933] hda: 488397168 sectors (250059 MB) w/8192KiB Cache, 
CHS=30401/255/63

[5.400233] hda: cache flushes supported
[5.400416]  hda: hda1 hda2 hda3
[5.409031] hdb: max request size: 512KiB
[5.427436] hdb: 625142448 sectors (320072 MB) w/8192KiB Cache, 
CHS=38913/255/63

[5.431315] hdb: cache flushes supported
[5.431490]  hdb: hdb1
[5.445991] hdc: max request size: 512KiB
[5.461190] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, 
CHS=30401/255/63

[5.461458] hdc: cache flushes supported
[5.461649]  hdc: hdc1 hdc2 hdc3
[5.470501] hdd: max request size: 512KiB
[5.488660] hdd: 390721968 sectors (200049 MB) w/8192KiB Cache, 
CHS=24321/255/63

[5.49085

Bug#504007: linux-image-2.6.26-1-686: Thinkpad T43 also does not boot

[Walter Landry]

Package: linux-image-2.6.26-1-686
Version: 2.6.26-8
Followup-For: Bug #504007

My laptop, a Thinkpad T43, has the exact same behavior: lots of dots and 
then it hangs.  So it is not specific to the Acer.  I also use LILO, 
and all of my partitions use XFS.  The 2.6.25-2 kernel still works 
fine.

Cheers,
Walter Landry
[EMAIL PROTECTED]


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92j  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.26-1-686 recommends:
ii  libc6-i6862.7-15 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.26-1-686 suggests:
ii  lilo  1:22.8-6   LInux LOader - The Classic OS load
pn  linux-doc-2.6.26   (no description available)

-- debconf information:
  linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false
  linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false
  linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: severity of 504116 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> severity 504116 important
Bug#504116: linux-image-2.6.24-etchnhalf.1-686: RAID1 broken after upgrading 
kernel to 2.6.24-etchnhalf
Severity set to `important' from `grave'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#504116: linux-image-2.6.24-etchnhalf.1-686: RAID1 broken after upgrading kernel to 2.6.24-etchnhalf

[Olaf Zaplinski]

Package: linux-image-2.6.24-etchnhalf.1-686
Version: 2.6.24-6~etchnhalf.6
Severity: grave
Justification: causes non-serious data loss

upgraded from 2.6.18 to 2.6.24-etchnhalf on i686 machine, afterwards all my 
RAID1 volumes were broken:


Personalities : [raid1] 
md3 : active raid1 hda6[0]
1100352 blocks [2/1] [U_]

md2 : active raid1 hda5[0]
1060160 blocks [2/1] [U_]

md1 : active raid1 hda2[0]
1959808 blocks [2/1] [U_]

md0 : active raid1 hda1[0]
40064 blocks [2/1] [U_]

Reason: /dev/hda is running fine (PIIX4), but /dev/sda on 53c875 is missing in 
the RAID setup.
It is accessible:

binky:~# fdisk -l /dev/sda

Disk /dev/sda: 4335 MB, 4335206400 bytes
255 heads, 63 sectors/track, 527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[--snip--]


but the RAID setup is broken.



-- Package-specific info:
** Version:
Linux version 2.6.24-etchnhalf.1-686 (Debian 2.6.24-6~etchnhalf.6) ([EMAIL 
PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP 
Mon Oct 13 07:27:05 UTC 2008

** Command line:
auto BOOT_IMAGE=Linux ro root=901 lapic reboot=warm

** Not tainted

** Kernel log:
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt :00:07.2[D] -> Link [LNKD] -> GSI 12 (level, low) -> 
IRQ 12
uhci_hcd :00:07.2: UHCI Host Controller
uhci_hcd :00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd :00:07.2: irq 12, io base 0xe000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hda: max request size: 128KiB
hda: 8467200 sectors (4335 MB) w/96KiB Cache, CHS=8400/16/63
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
scsi 0:0:0:0: Direct-Access IBM  DCAS-34330W  S65A PQ: 0 ANSI: 2
 target0:0:0: tagged command queuing enabled, command queue depth 16.
 target0:0:0: Beginning Domain Validation
 target0:0:0: asynchronous
 target0:0:0: wide asynchronous
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
 target0:0:0: Domain Validation skipping write tests
 target0:0:0: Ending Domain Validation
scsi 0:0:2:0: Sequential-Access TANDBERG SLR6 0404 PQ: 0 ANSI: 2
 target0:0:2: Beginning Domain Validation
 target0:0:2: asynchronous
 target0:0:2: wide asynchronous
 target0:0:2: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
 target0:0:2: Domain Validation skipping write tests
 target0:0:2: Ending Domain Validation
Probing IDE interface ide1...
md: raid1 personality registered for level 1
md: md0 stopped.
md: bind
raid1: raid set md0 active with 1 out of 2 mirrors
md: md1 stopped.
md: bind
raid1: raid set md1 active with 1 out of 2 mirrors
md: md2 stopped.
md: bind
raid1: raid set md2 active with 1 out of 2 mirrors
md: md3 stopped.
md: bind
raid1: raid set md3 active with 1 out of 2 mirrors
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
st: Version 20070203, fixed bufsize 32768, s/g segs 256
Driver 'st' needs updating - please use bus_type methods
st 0:0:2:0: Attached scsi tape st0
st 0:0:2:0: st0: try direct i/o: yes (alignment 512 B)
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 8467200 512-byte hardware sectors (4335 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
DPO or FUA
sd 0:0:0:0: [sda] 8467200 512-byte hardware sectors (4335 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
osst :I: Tape driver with OnStream support version 0.99.4
osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $
Driver 'osst' needs updating - please use bus_type methods
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
input: PC Speaker as /class/input/input0
Linux agpgart interface v0.102
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xd000
piix4_smbus :00:07.3: Found :00:07.3 device
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
input: Power Button (FF) as /class/input/input1
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input2
ACPI: Power Button (CM) [PWRB]
Adding 72284k swap on /dev/hda3.  Priority:42 extents:1 across:72284k
Adding 72284k swap on /dev/sda3.  Priority:42 extents:1 across:72284k
EXT3 FS on md1, internal journal
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: [EMAIL PROTECTED]
kjournald starting.  Commit interval 5 seconds
EXT3

Processed: Re: Bug#502346: virtualbox-ose-modules package older than virtualbox-ose

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 502346 virtualbox-ose 1.6.6-dfsg-2
Bug#502346: virtualbox-ose-modules package older than virtualbox-ose
Bug#502539: virtualbox-ose-modules-2.6.26-1-686 contains outdated module for 
VirtualBox
Bug reassigned from package `linux-modules-extra-2.6' to `virtualbox-ose'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#502346: virtualbox-ose-modules package older than virtualbox-ose

[Bastian Blank]

reassign 502346 virtualbox-ose 1.6.6-dfsg-2
thanks

On Wed, Oct 29, 2008 at 02:34:45PM +0100, Frans Pop wrote:
> I'm reopening the BR as the virtualbox-ose kernel modules in testing are 
> still not usable with the version of virtualbox-ose in testing.

Changing the API without a soname or some other identifier which can and
has to be used in a dependency is unacceptable. Reassigning.

Bastian

-- 
Oh, that sound of male ego.  You travel halfway across the galaxy and
it's still the same song.
-- Eve McHuron, "Mudd's Women", stardate 1330.1



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#488669: sparc X server bug

[Daniel Smolik]

Gaudenz Steinlin napsal(a):

On Thu, Oct 30, 2008 at 09:37:47PM +0100, Daniel Smolik wrote:

Gaudenz Steinlin napsal(a):
I downgraded Xorg to SID and there is a result:

==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 21:36:11 2008
(++) Using config file: "/root/xorg.conf.new"
(WW) INVALID MEM ALLOCATION b: 0x2 e: 0x3 correcting
mmap failure: Invalid argument

Fatal server error:
xf86MapDomainMem():  mmap() failure



The X server in unstable is expected to not work without the patch. It should
behave the same as the kernel in testing in this regard.


sunik:~# uname -a
Linux sunik 2.6.26-1-sparc64 #1 Sun Oct 26 17:42:45 UTC 2008 sparc64 GNU/Linux

I mean that patch doesn't help.


That's strange, because others report that the patch fixes the problem. I'm a 
bit
lost now and it's difficult to further debug this without the proper hardware.
Are you really sure that you are running the patched kernel and that you are 
not running the kernel from lenny or unstable? 

I run kernel that I downloaded from your site. May be problem is that E250 i 
multi domain PCI machine.
Have other people the same HW as I or eg. Ultra 10 or 5 ?

Regards
Dan






Gaudenz



Dan





I must say again that problem on SPARC machines with Xorg is problem  
with Xorg not with kernel.
In principle I agree with you. But to fix the X server side of the  
problem we would have to upgrade to the X server currently in  
experimental. I don't think that it's possible to upgrade lenny to

this version at this moment right before the release. So I'm trying to find
out if the problem is also solved by reverting the problematic kernel  
change.


And as you have noticed yourself, the X server in experimental has other
problems. So it's not really suitable for a release.

Please look at  http://lkml.org/lkml/2008/6/3/147 


I'm already aware of this.

Gaudenz



--
Mydatex s r.o.
http://www.mydatex.cz
email: [EMAIL PROTECTED]
mob: 604200362
tel: 226210085





--
Mydatex s r.o.
http://www.mydatex.cz
email: [EMAIL PROTECTED]
mob: 604200362
tel: 226210085



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#488669: sparc X server bug

[Gaudenz Steinlin]

On Thu, Oct 30, 2008 at 09:37:47PM +0100, Daniel Smolik wrote:
> Gaudenz Steinlin napsal(a):
> I downgraded Xorg to SID and there is a result:
>
> ==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 30 21:36:11 2008
> (++) Using config file: "/root/xorg.conf.new"
> (WW) INVALID MEM ALLOCATION b: 0x2 e: 0x3 correcting
> mmap failure: Invalid argument
>
> Fatal server error:
> xf86MapDomainMem():  mmap() failure
>

The X server in unstable is expected to not work without the patch. It should
behave the same as the kernel in testing in this regard.

> sunik:~# uname -a
> Linux sunik 2.6.26-1-sparc64 #1 Sun Oct 26 17:42:45 UTC 2008 sparc64 GNU/Linux
>
> I mean that patch doesn't help.

That's strange, because others report that the patch fixes the problem. I'm a 
bit
lost now and it's difficult to further debug this without the proper hardware.
Are you really sure that you are running the patched kernel and that you are 
not running the kernel from lenny or unstable? 

Gaudenz

>
>
> Dan
>
>
>
>
>
>>
>>> I must say again that problem on SPARC machines with Xorg is problem  
>>> with Xorg not with kernel.
>>
>> In principle I agree with you. But to fix the X server side of the  
>> problem we would have to upgrade to the X server currently in  
>> experimental. I don't think that it's possible to upgrade lenny to
>> this version at this moment right before the release. So I'm trying to find
>> out if the problem is also solved by reverting the problematic kernel  
>> change.
>>
>> And as you have noticed yourself, the X server in experimental has other
>> problems. So it's not really suitable for a release.
>>> Please look at  http://lkml.org/lkml/2008/6/3/147 
>>> 
>>
>> I'm already aware of this.
>>
>> Gaudenz
>>
>
>
> -- 
> Mydatex s r.o.
> http://www.mydatex.cz
> email: [EMAIL PROTECTED]
> mob: 604200362
> tel: 226210085

-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek! page_mapcount(page) went negative! (-1))

[Hans van Kranenburg]

Bastian Blank wrote:

On Fri, Oct 31, 2008 at 12:54:14PM +0100, Lars Michael Jogback wrote:

* Bastian Blank <[EMAIL PROTECTED]> [2008-10-31 12:47:34]:

Okay, so I have no further possibilities except removing the kernel.

Do you know if there is someplace to download the OpenSUSE-kernel to test
and see if the error is present in that too?


The SuSE kernels can be found at 
http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/. But as the

next SLES will ship .27, they don't really care.


A related bugreport I found when searching for this error two weeks ago 
is an ubuntu bug report in launchpad. [1] It has a syslog-excerpt 
attachted [2] showing the use of kernel 2.6.27. (kernel BUG at [..] 
linux-2.6.27/mm/rmap.c:662)


There's also [3] on ubuntuforums, reported about 16 hours ago, same 
kernel, same error etc...


So I guess whatever is broken, it's in our 2.6.27 as well.

Hans van Kranenburg

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/252977
[2] http://launchpadlibrarian.net/17573131/syslog-2009-09-12.txt
[3] http://ubuntuforums.org/showthread.php?t=964133



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Scheduling linux-2.6 2.6.22-4

[Andreas Barth]

* Sven Luther ([EMAIL PROTECTED]) [070830 06:16]:
> I would like to know if this upload would include the efika patches that
> where included in the subversion repository after the 2.6.22-3 upload,
> or if you will silently disable them, after you kicked me out of the
> debian-kernel team without reasonable justification or even trying to
> speak to me.

Sorry for following up so late on this bug report.


I just asked on IRC:

16:25 < aba> can someone comment on http://bugs.debian.org/439006
16:25 < aba> (Efika and sony PS3 patches in linux-2.6)
16:49 < waldi> aba: both efika and ps3 support is maintained in the
  linus tree since a long time. so it is possible to fix serious
  problems with the linux upstream stable updates and don't need to
  duplicate the work. ps3 support was enabled by me for 2.6.26, so
  sven tried to fix not enabled things
16:49 < aba> waldi: so, are the issues reported there now already
  resolved? or are they "not relevant anymore"? or ...?
16:50 < waldi> sven did not further try to push massive patch sets,
  which was just about to be submitted to the ppc maintainer, for
  inclusion into linux-2.6
16:51 < waldi> the support is upstream and from what I know working, so:
  "not relevant anymore"


Is this correct? If so, I would like to close this bug report now. Sorry
for the late response.



Cheers,
Andi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: severity of 500358 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> severity 500358 important
Bug#500358: mach64 stopped working on the Sun Ultra 5 graphics card after 
upgrade
Bug#488669: kernel changes break X on sparc64/pci
Severity set to `important' from `grave'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek! page_mapcount(page) went negative! (-1))

[Bastian Blank]

On Fri, Oct 31, 2008 at 12:54:14PM +0100, Lars Michael Jogback wrote:
> * Bastian Blank <[EMAIL PROTECTED]> [2008-10-31 12:47:34]:
> > Okay, so I have no further possibilities except removing the kernel.
> Do you know if there is someplace to download the OpenSUSE-kernel to test
> and see if the error is present in that too?

The SuSE kernels can be found at 
http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/. But as the
next SLES will ship .27, they don't really care.

Bastian

-- 
Pain is a thing of the mind.  The mind can be controlled.
-- Spock, "Operation -- Annihilate!" stardate 3287.2



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#498271: linux-image-2.6.26-1-amd64: the SATA CDROM isn't detected

[Dieter Faulbaum]

Dieter Faulbaum <[EMAIL PROTECTED]> writes:

> Subject: linux-image-2.6.26-1-amd64: the SATA CDROM isn't detected
> Package: linux-image-2.6.26-1-amd64
> Version: 2.6.26-4
> Severity: important

Here
http://lkml.org/lkml/2008/8/20/51


I found this patch from Tejun Heo:

--- a/drivers/ata/sata_nv.c
+++ b/drivers/ata/sata_nv.c
@@ -309,8 +309,6 @@ static void nv_nf2_freeze(struct ata_port *ap);
 static void nv_nf2_thaw(struct ata_port *ap);
 static void nv_ck804_freeze(struct ata_port *ap);
 static void nv_ck804_thaw(struct ata_port *ap);
-static int nv_hardreset(struct ata_link *link, unsigned int *class,
-   unsigned long deadline);
 static int nv_adma_slave_config(struct scsi_device *sdev);
 static int nv_adma_check_atapi_dma(struct ata_queued_cmd *qc);
 static void nv_adma_qc_prep(struct ata_queued_cmd *qc);
@@ -407,7 +405,7 @@ static struct scsi_host_template nv_swncq_sht = {
 
 static struct ata_port_operations nv_generic_ops = {
.inherits   = &ata_bmdma_port_ops,
-   .hardreset  = nv_hardreset,
+   .hardreset  = ATA_OP_NULL,
.scr_read   = nv_scr_read,
.scr_write  = nv_scr_write,
 };
@@ -1588,21 +1586,6 @@ static void nv_mcp55_thaw(struct ata_port *ap)
ata_sff_thaw(ap);
 }
 
-static int nv_hardreset(struct ata_link *link, unsigned int *class,
-   unsigned long deadline)
-{
-   int rc;
-
-   /* SATA hardreset fails to retrieve proper device signature on
-* some controllers.  Request follow up SRST.  For more info,
-* see http://bugzilla.kernel.org/show_bug.cgi?id=3352
-*/
-   rc = sata_sff_hardreset(link, class, deadline);
-   if (rc)
-   return rc;
-   return -EAGAIN;
-}
-
 static void nv_adma_error_handler(struct ata_port *ap)
 {
struct nv_adma_port_priv *pp = ap->private_data;


which works for me (with a stock kernel 2.6.27.4), so
that I can use my cdrom again.

Maybe this patch should be included into the debian kernel?


-- 
Dieter Faulbaum



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#500358:

[Max Dmitrichenko]

Proposed patch. Explanations here [1].

[1] http://marc.info/?l=linux-kernel&m=122545873605649&w=2

--
  Max
diff -uprN linux-source-2.6.26/arch/sparc64/kernel/pci.c linux-source-2.6.26.pci-fixed/arch/sparc64/kernel/pci.c
--- linux-source-2.6.26/arch/sparc64/kernel/pci.c	2008-07-14 01:51:29.0 +0400
+++ linux-source-2.6.26.pci-fixed/arch/sparc64/kernel/pci.c	2008-10-31 01:23:54.0 +0300
@@ -1017,6 +1017,7 @@ static int __pci_mmap_make_offset(struct
 
 	for (i = 0; i <= PCI_ROM_RESOURCE; i++) {
 		struct resource *rp = &pdev->resource[i];
+		resource_size_t aligned_end;
 
 		/* Active? */
 		if (!rp->flags)
@@ -1034,8 +1035,15 @@ static int __pci_mmap_make_offset(struct
 continue;
 		}
 
+		/* Align the resource end to the next page address.
+ * PAGE_SIZE intentionally added instead of (PAGE_SIZE - 1),
+ * because actually we need the address of the next byte
+ * after rp->end.
+ */
+		aligned_end = (rp->end + PAGE_SIZE) & PAGE_MASK;
+
 		if ((rp->start <= user_paddr) &&
-		(user_paddr + user_size) <= (rp->end + 1UL))
+		(user_paddr + user_size) <= aligned_end)
 			break;
 	}
 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 500358 = patch
Bug#500358: mach64 stopped working on the Sun Ultra 5 graphics card after 
upgrade
Tags were: help moreinfo
Bug#488669: kernel changes break X on sparc64/pci
Tags set to: patch

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 500358 linux-2.6
Bug#500358: mach64 stopped working on the Sun Ultra 5 graphics card after 
upgrade
Bug#488669: kernel changes break X on sparc64/pci
Bug reassigned from package `xserver-xorg-core' to `linux-2.6'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Possibility for dependencies against specific kernel modules

[Kel Modderman]

On Friday 31 October 2008 22:20:26 Josselin Mouette wrote:
> Le vendredi 31 octobre 2008 à 12:44 +0100, Bastian Blank a écrit :
> > Because of some recent events, I thought about the possibility for
> > packages to depend against kernel module packages. As we don't want to
> > dictate the usage of Debian provided kernels, we need a last resort
> > fallback to the modules source.
> 
> I think this is something good to have, but I’m skeptical about the
> fallback to the source. It will, in unstable and sometimes in testing or
> even stable, to situations where the modules are not available for a
> while, and the source will get installed, leaving the system in a broken
> state. Unless the source can use DKMS or a similar mechanism to
> automatically generate modules, this is not very reliable.
> 

fwiw, I have tried to address the issue of having $module-source packages
have their binary product built and installed rather transparently, you may
look at the initial hackwork at:

http://svn.berlios.de/svnroot/repos/fullstory/dmakms/trunk/
http://svn.berlios.de/svnroot/repos/fullstory/dmakms/trunk/debian/README.Debian

It's the start of a solution for: #299727

dmakms has got technical flaws, I know, but it works well enough for my current
needs (without patching existing tools such as module-assistant, which could
probably do with some lovin'), maybe it could be extended and fixed up to be
technically better and useful for others.

Thanks, Kel.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek! page_mapcount(page) went negative! (-1))

[Lars Michael Jogback]

* Bastian Blank <[EMAIL PROTECTED]> [2008-10-31 12:47:34]:

> On Fri, Oct 31, 2008 at 08:49:42AM +0100, Lars Michael Jogback wrote:
> > * Bastian Blank <[EMAIL PROTECTED]> [2008-10-30 10:50:03]:
> > > I comitted a workaround, to be exact an update for a workaround. I was
> > > not longer able to trigger that under load. Please test the snapshots[1]
> > > tomorrow (2.6.26-10~snapshot.12362 or higher).
> > Now I've tested the workaround, and I'm sorry to say that it doesn't help.
> 
> Okay, so I have no further possibilities except removing the kernel.
> 

Do you know if there is someplace to download the OpenSUSE-kernel to test
and see if the error is present in that too? If it is, there might be more
kernel-hackers that have idea's on what the problem might be?

Best Regards,
/LM




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Possibility for dependencies against specific kernel modules

[Josselin Mouette]

Le vendredi 31 octobre 2008 à 12:44 +0100, Bastian Blank a écrit :
> Because of some recent events, I thought about the possibility for
> packages to depend against kernel module packages. As we don't want to
> dictate the usage of Debian provided kernels, we need a last resort
> fallback to the modules source.

I think this is something good to have, but I’m skeptical about the
fallback to the source. It will, in unstable and sometimes in testing or
even stable, to situations where the modules are not available for a
while, and the source will get installed, leaving the system in a broken
state. Unless the source can use DKMS or a similar mechanism to
automatically generate modules, this is not very reliable.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek! page_mapcount(page) went negative! (-1))

[Bastian Blank]

On Fri, Oct 31, 2008 at 08:49:42AM +0100, Lars Michael Jogback wrote:
> * Bastian Blank <[EMAIL PROTECTED]> [2008-10-30 10:50:03]:
> > I comitted a workaround, to be exact an update for a workaround. I was
> > not longer able to trigger that under load. Please test the snapshots[1]
> > tomorrow (2.6.26-10~snapshot.12362 or higher).
> Now I've tested the workaround, and I'm sorry to say that it doesn't help.

Okay, so I have no further possibilities except removing the kernel.

Bastian

-- 
... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
-- McCoy, "The Omega Glory", stardate unknown



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Possibility for dependencies against specific kernel modules

[Bastian Blank]

Hi folks

Because of some recent events, I thought about the possibility for
packages to depend against kernel module packages. As we don't want to
dictate the usage of Debian provided kernels, we need a last resort
fallback to the modules source.

My first solution was something like the following:

| Package: test
| Depends: test-modules | test-source
|
| Package: test-modules
| Depends: linux-image-2.6.26-1-powerpc | linux-image-2.6.26-1-powerpc64
|
| Package: test-source

Both apt and aptitude would always try to install test-modules. The
problem is that neither apt nor aptitude are smart enough to find the
best solution in the dependency tree, both only evaluate deps of depth 1
at one time.

I found a variant which seems to work, but produces dependency packages
for fun:

| Package: test
| Depends: test-modules-fallback
|
| Package: test-modules-fallback
| Depends: test-modules | test-source, linux-image-2.6.26-1-powerpc | 
linux-image-2.6.26-1-powerpc64 | test-source
|
| Package: test-modules
| Depends: linux-image-2.6.26-1-powerpc | linux-image-2.6.26-1-powerpc64
|
| Package: test-source

Now the question is clearly, do we want/need such a possibility? And if
yes, how should it work. If the answer is no, I have to refuse to build
modules like vbox[1].

Bastian

[1]: The virtualbox modules don't define a stable ABI, it actually
 changes for every release.
-- 
Virtue is a relative term.
-- Spock, "Friday's Child", stardate 3499.1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#504093: drbd8-modules-2.6.26-1-xen-686: module doesn't load

[zak82]

Package: drbd8-modules-2.6.26-1-xen-686
Version: 2.6.26+8.0.13-4
Severity: grave
Justification: renders package unusable

Hi,

drbd8-modules-2.6.26-1-xen-686: module doesn't load
Please update binary to actual kernel.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-xen-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages drbd8-modules-2.6.26-1-xen-686 depends on:
ii  linux-modules-2.6.26-1-xen-68 2.6.26-8   Linux 2.6.26 modules on i686

drbd8-modules-2.6.26-1-xen-686 recommends no packages.

drbd8-modules-2.6.26-1-xen-686 suggests no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#503821: linux-image-2.6.26-1-xen-amd64: Kernel crash in Dom0 (Eeek! page_mapcount(page) went negative! (-1))

[Lars Michael Jogback]

* Bastian Blank <[EMAIL PROTECTED]> [2008-10-30 10:50:03]:

> I comitted a workaround, to be exact an update for a workaround. I was
> not longer able to trigger that under load. Please test the snapshots[1]
> tomorrow (2.6.26-10~snapshot.12362 or higher).

Now I've tested the workaround, and I'm sorry to say that it doesn't help.

[0.00] Linux version 2.6.26-1-xen-amd64 (Debian 
2.6.26-10~snapshot.12362) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 
(prerelease) (Debian 4.1.2-23+1)) #1 SMP Fri Oct 31 03:53:45 UTC 2008

[  200.424526] Eeek! page_mapcount(page) went negative! (-1)
[  200.424637]   page pfn = 4
[  200.424937]   page->flags = 0
[  200.424937]   page->count = 0
[  200.424937]   page->mapping = 
[  200.424937]   vma->vm_ops = 0x0
[  200.424937] [ cut here ]
[  200.424937] kernel BUG at mm/rmap.c:673!
[  200.424937] invalid opcode:  [1] SMP
[  200.425856] CPU 0
[  200.425856] Modules linked in: bridge netloop video output ac battery 
microcode firmware_class nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc 
ipv6 xfs reiserfs ext2 sha256_generic aes_x86_64 aes_generic cbc dm_crypt 
crypto_blkcipher raid456 async_xor async_memcpy async_tx xor loop iTCO_wdt 
serio_raw pcspkr i2c_i801 psmouse rng_core i2c_core container shpchp 
pci_hotplug button i3000_edac edac_core evdev joydev ext3 jbd mbcache dm_mirror 
dm_log dm_snapshot dm_mod raid1 md_mod ide_cd_mod cdrom ide_pci_generic usbhid 
hid ff_memless piix ata_piix ide_core sd_mod floppy ata_generic ehci_hcd 
uhci_hcd sata_sil24 libata 3w_9xxx dock e1000e scsi_mod thermal processor fan 
thermal_sys
[  200.429852] Pid: 6332, comm: a.out Not tainted 2.6.26-1-xen-amd64 #1
[  200.429852] RIP: e030:[]  [] 
page_remove_rmap+0xfb/0x117
[  200.429852] RSP: e02b:880071aabdc8  EFLAGS: 00010246
[  200.429852] RAX:  RBX: 88000235a0e0 RCX: 80501fc8
[  200.429852] RDX: ff5f7000 RSI: 0001 RDI: 80501fc0
[  200.429852] RBP: 880071a577c8 R08: 80501fb0 R09: 880001b48f08
[  200.429852] R10: 880071aaba58 R11: 00015382 R12: 88000235a0e0
[  200.429852] R13: 88c010d8 R14: 88007d426840 R15: 880002384048
[  200.429852] FS:  7f41ff3e36e0() GS:80539000() 
knlGS:
[  200.429852] CS:  e033 DS:  ES: 
[  200.429852] DR0:  DR1:  DR2: 
[  200.429852] DR3:  DR6: 0ff0 DR7: 0400
[  200.429852] Process a.out (pid: 6332, threadinfo 880071aaa000, task 
880071ad8500)
[  200.429852] Stack:  8800717f08d0 4800 00322061b000 
80273239
[  200.429852]  0206  880071aabec8 

[  200.429852]   880071a577c8 880071aabed0 
0003628e
[  200.429852] Call Trace:
[  200.429852]  [] ? unmap_vmas+0x744/0xa49
[  200.429852]  [] ? exit_mmap+0x7b/0xf7
[  200.429852]  [] ? mmput+0x2c/0xc0
[  200.429852]  [] ? do_exit+0x25a/0x6ce
[  200.429852]  [] ? do_group_exit+0xa6/0xdc
[  200.429852]  [] ? system_call+0x68/0x6d
[  200.429852]  [] ? system_call+0x0/0x6d
[  200.429852]
[  200.429852]
[  200.429852] Code: 80 e8 18 0c fd ff 48 8b 85 90 00 00 00 48 85 c0 74 19 48 
8b 40 20 48 85 c0 74 10 48 8b 70 58 48 c7 c7 e1 52 4b 80 e8 f3 0b fd ff <0f> 0b 
eb fe 8b 77 18 41 58 5b 5d 83 e6 01 f7 de 83 c6 04 e9 64
[  200.429852] RIP  [] page_remove_rmap+0xfb/0x117
[  200.429852]  RSP 
[  200.439529] ---[ end trace 10482cbe68c8d062 ]---
[  200.439619] Fixing recursive fault but reboot is needed!

My ugly testprogram crashed directly on this one aswell.

Best Regards,
/LM



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#503821: Snapshot fails to solve the issue

[Kapil Hari Paranjape]

Hello,

On Thu, 30 Oct 2008, Bastian Blank wrote:
> I comitted a workaround, to be exact an update for a workaround. I was
> not longer able to trigger that under load. Please test the snapshots[1]
> tomorrow (2.6.26-10~snapshot.12362 or higher).

Unfortunately, this did not work for me.

I downloaded:

http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/
linux-image-2.6.26-1-xen-amd64_2.6.26-10~snapshot.12362_amd64.deb

It continues to give errors as documented before ... i. e. 
On Wed, 29 Oct 2008, in <[EMAIL PROTECTED]> I wrote:
> I tested this with the following configurations where except for the
> kernel everthing else is from lenny (including the xen hypervisor
> which is 3.2). The kernels are the stock kernels from Debian.
> 
>  dom0 kernel   domU kernel  result
>  2.6.18-6-xen-amd642.6.18-6-xen-amd64   no crash
>  2.6.26-1-xen-amd642.6.26-1-xen-amd64   crash for domU and dom0
>  2.6.18-6-xen-amd642.6.26-1-xen-amd64   crash for domU
>  2.6.26-1-xen-amd642.6.18-6-xen-amd64   crash for dom0

The "crash" signifies a kernel oops when running the test program
given by Lars in Message-Id: <[EMAIL PROTECTED]>
on this list.

Regards,

Kapil.
--



signature.asc
Description: Digital signature