Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #51789 > unrolled thread

Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

Back to article view | Back to linux.debian.kernel

Contents

  Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Robert Henney <robh@rut.org> - 2015-12-18 02:10 +0100
    Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Ben Hutchings <ben@decadent.org.uk> - 2015-12-18 05:30 +0100
      Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Robert Henney <robh@rut.org> - 2015-12-18 14:10 +0100
        Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Ben Hutchings <ben@decadent.org.uk> - 2015-12-18 14:30 +0100
          Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Robert Henney <robh@rut.org> - 2015-12-18 14:40 +0100
            Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Ben Hutchings <ben@decadent.org.uk> - 2015-12-18 14:40 +0100
              Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update Robert Henney <robh@rut.org> - 2015-12-18 16:30 +0100
    Processed: Re: Bug#808266: linux-image-3.2.0-4-686-pae: i386  Wheezy JFS broken in 3.2.73-2+deb7u1 security update owner@bugs.debian.org (Debian Bug Tracking System) - 2015-12-18 05:30 +0100
    Bug#808266: marked as done (linux-image-3.2.0-4-686-pae: i386  Wheezy JFS broken in 3.2.73-2+deb7u1 security update) owner@bugs.debian.org (Debian Bug Tracking System) - 2015-12-28 09:00 +0100

#51789 — Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

Package: src:linux
Version: 3.2.73-2+deb7u1
Severity: important

Today's kernel security update appears to have broken JFS support on i386, though JFS
still appears to be working on x86_64.

# mount -t jfs /dev/sda1 /mnt
mount: unknown filesystem type 'jfs'

# modprobe jfs
ERROR: could not insert 'jfs': Unknown symbol in module, or unknown parameter (see dmesg)

# dmesg|grep jfs
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)

after downgrading to 3.2.68-1+deb7u3 JFS works again, but then after re-upgrading to
3.2.73-2+deb7u1 JFS support is again broken.


-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.68-1+deb7u3

** Command line:
root=/dev/md/md_1 ro printk.time=0 raid=noautodetect acpi_enforce_resources=lax 

** Not tainted

** Kernel log:
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 1:0:0:0: [sda] Attached SCSI disk
sd 5:0:0:0: [sde] 117231408 512-byte logical blocks: (60.0 GB/55.8 GiB)
sd 5:0:0:0: [sde] Write Protect is off
sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: Attached scsi generic sg3 type 0
sd 5:0:0:0: Attached scsi generic sg4 type 0
 sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI disk
 sdd: sdd1 sdd2 < sdd5 sdd6 sdd7 >
sd 4:0:0:0: [sdd] Attached SCSI disk
 sde: sde1 sde2 < sde5 sde6 sde7 >
sd 5:0:0:0: [sde] Attached SCSI disk
 sdc: unknown partition table
sd 3:0:0:0: [sdc] Attached SCSI disk
md: md_d127 stopped.
md: bind<sdd>
md: bind<sde>
md: kicking non-fresh sdd from array!
md: unbind<sdd>
md: export_rdev(sdd)
md: raid1 personality registered for level 1
bio: create slab <bio-1> at 1
md/raid1:md_d127: active with 1 out of 2 mirrors
md_d127: detected capacity change from 0 to 9104973824
 md_d127: p1 p2 < p5 p6 p7 >
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md_d127p1): mounted filesystem with ordered data mode
udevd[356]: starting version 175
Marking TSC unstable due to TSC halts in idle
ACPI: acpi_idle registered with cpuidle
Switching to clocksource acpi_pm
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
powernow: No powernow capabilities detected
input: PC Speaker as /devices/platform/pcspkr/input/input2
parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
parport_pc: Current parallel port base: 0x0
parport_pc: VIA parallel port disabled in BIOS
ACPI: resource vt596_smbus [io  0xe800-0xe807] conflicts with ACPI region SM00 [io 0xe800-0xe806]
ACPI: This conflict may cause random problems and system instability
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
via686a 0000:00:04.4: Sensors disabled, enable with force_addr=0xe200
Error: Driver 'pcspkr' is already registered, aborting...
Adding 393556k swap on /dev/md_d127p7.  Priority:-1 extents:1 across:393556k 
EXT3-fs (md_d127p1): using internal journal
loop: module loaded
md: md_d126 stopped.
md: bind<sdd>
md/raid1:md_d126: active with 1 out of 2 mirrors
md_d126: detected capacity change from 0 to 9104973824
 md_d126: p1 p2 < p5 p6 p7 >
kjournald starting.  Commit interval 60 seconds
EXT3-fs (md_d127p5): using internal journal
EXT3-fs (md_d127p5): mounted filesystem with ordered data mode
kjournald starting.  Commit interval 120 seconds
EXT3-fs (md_d127p6): using internal journal
EXT3-fs (md_d127p6): mounted filesystem with ordered data mode
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)
e100 0000:02:05.0: firmware: agent loaded e100/d101m_ucode.bin into memory
ADDRCONF(NETDEV_UP): eth1: link is not ready
e100 0000:02:05.0: eth1: NIC Link is Up 100 Mbps Full Duplex
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
e100 0000:02:04.0: firmware: agent loaded e100/d101m_ucode.bin into memory
ADDRCONF(NETDEV_UP): eth0: link is not ready
e100 0000:02:04.0: eth0: NIC Link is Up 100 Mbps Full Duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (3975 buckets, 15900 max)
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
IPv6 over IPv4 tunneling driver
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)
jfs: Unknown symbol __bread_gfp (err 0)
jfs: Unknown symbol __getblk_gfp (err 0)

** Model information
not available

** Loaded modules:
sit
tunnel4
ppdev
lp
iptable_nat
nf_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_conntrack
ip_tables
x_tables
nfsd
nfs
nfs_acl
auth_rpcgss
fscache
lockd
sunrpc
w83781d
hwmon_vid
loop
snd_pcm
snd_page_alloc
snd_timer
snd
soundcore
via686a
i2c_viapro
parport_pc
pcspkr
evdev
parport
i2c_core
serio_raw
button
shpchp
processor
thermal_sys
ext3
mbcache
jbd
raid1
md_mod
sg
sd_mod
crc_t10dif
ata_generic
pata_pdc202xx_old
pata_via
sata_sil24
libata
uhci_hcd
ehci_hcd
usbcore
e100
floppy
scsi_mod
mii
usb_common

** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] [1106:0305] (rev 02)
	Subsystem: ASUSTeK Computer Inc. A7V Mainboard [1043:8033]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+ INTx-
	Latency: 8
	Region 0: Memory at e6000000 (32-bit, prefetchable) [size=32M]
	Capabilities: <access denied>
	Kernel driver in use: agpgart-via

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] [1106:8305] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: e3800000-e5dfffff
	Prefetchable memory behind bridge: e5f00000-e5ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 22)
	Subsystem: ASUSTeK Computer Inc. A7V Mainboard [1043:8033]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Kernel driver in use: parport_pc

00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 10) (prog-if 8a [Master SecP PriP])
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at b800 [size=16]
	Capabilities: <access denied>

00:04.3 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 10) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. (Wrong ID) VA-502 Mainboard [0925:1234]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin D routed to IRQ 15
	Region 4: I/O ports at b000 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:04.4 Bridge [0680]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] (rev 30)
	Subsystem: ASUSTeK Computer Inc. A7V Mainboard [1043:8033]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin ? routed to IRQ 9
	Capabilities: <access denied>

00:0a.0 PCI bridge [0604]: Intel Corporation 21154 PCI-to-PCI Bridge [8086:b154] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
	I/O behind bridge: 00008000-00008fff
	Memory behind bridge: e1800000-e37fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:0c.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller [1095:3124] (rev 02)
	Subsystem: Silicon Image, Inc. Device [1095:7124]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at e1000000 (64-bit, non-prefetchable) [size=128]
	Region 2: Memory at e0800000 (64-bit, non-prefetchable) [size=32K]
	Region 4: I/O ports at 7800 [size=16]
	[virtual] Expansion ROM at 10000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: sata_sil24

00:11.0 Mass storage controller [0180]: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) [105a:0d30] (rev 02)
	Subsystem: Promise Technology, Inc. Ultra100 [105a:4d33]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 10
	Region 0: I/O ports at 7400 [size=8]
	Region 1: I/O ports at 7000 [size=4]
	Region 2: I/O ports at 6800 [size=8]
	Region 3: I/O ports at 6400 [size=4]
	Region 4: I/O ports at 6000 [size=64]
	Region 5: Memory at e0000000 (32-bit, non-prefetchable) [size=128K]
	[virtual] Expansion ROM at 10080000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: pata_pdc202xx_old

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 3D Rage Pro AGP 1X/2X [1002:4742] (rev 5c) (prog-if 00 [VGA controller])
	Subsystem: Advanced Micro Devices [AMD] nee ATI Rage Pro Turbo AGP 2X [1002:0084]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: I/O ports at d800 [size=256]
	Region 2: Memory at e3800000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at e5fe0000 [disabled] [size=128K]
	Capabilities: <access denied>

02:04.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 08)
	Subsystem: Compaq Computer Corporation NC3134 Fast Ethernet NIC (dual port) [0e11:b163]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 12
	Region 0: Memory at e3000000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at 8800 [size=64]
	Region 2: Memory at e2800000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: e100

02:05.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 08)
	Subsystem: Compaq Computer Corporation NC3134 Fast Ethernet NIC (dual port) [0e11:b163]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 15
	Region 0: Memory at e2000000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at 8400 [size=64]
	Region 2: Memory at e1800000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: e100


** USB devices:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:9254 Alcor Micro Corp. Hub


-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.2.0-4-686-pae depends on:
ii  debconf [debconf-2.0]                   1.5.49
ii  initramfs-tools [linux-initramfs-tool]  0.109.1
ii  kmod                                    9-3
ii  linux-base                              3.5
ii  module-init-tools                       9-3

Versions of packages linux-image-3.2.0-4-686-pae recommends:
ii  firmware-linux-free  3.2
ii  libc6-i686           2.13-38+deb7u8

Versions of packages linux-image-3.2.0-4-686-pae suggests:
pn  debian-kernel-handbook     <none>
pn  grub-pc | extlinux | lilo  <none>
ii  linux-doc-3.2              3.2.73-2+deb7u1

Versions of packages linux-image-3.2.0-4-686-pae is related to:
pn  firmware-atheros        <none>
pn  firmware-bnx2           <none>
pn  firmware-bnx2x          <none>
pn  firmware-brcm80211      <none>
pn  firmware-intelwimax     <none>
pn  firmware-ipw2x00        <none>
pn  firmware-ivtv           <none>
pn  firmware-iwlwifi        <none>
pn  firmware-libertas       <none>
ii  firmware-linux          0.36+wheezy.1
ii  firmware-linux-nonfree  0.36+wheezy.1
pn  firmware-myricom        <none>
pn  firmware-netxen         <none>
pn  firmware-qlogic         <none>
pn  firmware-ralink         <none>
pn  firmware-realtek        <none>
pn  xen-hypervisor          <none>

-- debconf information:
  linux-image-3.2.0-4-686-pae/postinst/depmod-error-initrd-3.2.0-4-686-pae: false
  linux-image-3.2.0-4-686-pae/prerm/removing-running-kernel-3.2.0-4-686-pae: true
  linux-image-3.2.0-4-686-pae/postinst/missing-firmware-3.2.0-4-686-pae:
  linux-image-3.2.0-4-686-pae/postinst/ignoring-ramdisk:

[toc] | [next] | [standalone]

#51790

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Thu, 2015-12-17 at 19:20 -0500, Robert Henney wrote:
> Package: src:linux
> Version: 3.2.73-2+deb7u1
> Severity: important
> 
> Today's kernel security update appears to have broken JFS support on i386, though JFS
> still appears to be working on x86_64.
[...]

I don't think so.  Have you rebooted the i386 system yet?

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'

[toc] | [prev] | [next] | [standalone]

#51793

On Fri, Dec 18, 2015 at 04:20:49AM +0000, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Thu, 2015-12-17 at 19:20 -0500, Robert Henney wrote:
> > Package: src:linux
> > Version: 3.2.73-2+deb7u1
> > Severity: important
> > 
> > Today's kernel security update appears to have broken JFS support on i386, though JFS
> > still appears to be working on x86_64.
> [...]
> 
> I don't think so.  Have you rebooted the i386 system yet?
> 
> Ben.

When I said i386 earlier, I probably mean 686.

I rebooted following each of the re-installs of the linux-image-3.2.0-4-686-pae package,
switching between versions 3.2.68-1+deb7u3 and 3.2.73-2+deb7u1 of it.  Changing nothing
else, the jfs module loads and jfs partitions mount at boot with the earlier package
version, and with the latest package the jfs module fails to load and dmesg contains
those errors I mentioned.  Reproducable every time here, as I've switched the package 
between versions several times (rebooting after each) to confirm.

[toc] | [prev] | [next] | [standalone]

#51795

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2015-12-18 at 07:46 -0500, Robert Henney wrote:
> On Fri, Dec 18, 2015 at 04:20:49AM +0000, Ben Hutchings wrote:
> > Control: tag -1 moreinfo
> > 
> > On Thu, 2015-12-17 at 19:20 -0500, Robert Henney wrote:
> > > Package: src:linux
> > > Version: 3.2.73-2+deb7u1
> > > Severity: important
> > > 
> > > Today's kernel security update appears to have broken JFS support on i386, though JFS
> > > still appears to be working on x86_64.
> > [...]
> > 
> > I don't think so.  Have you rebooted the i386 system yet?
> > 
> > Ben.
> 
> When I said i386 earlier, I probably mean 686.
> 
> I rebooted following each of the re-installs of the linux-image-3.2.0-4-686-pae package,
> switching between versions 3.2.68-1+deb7u3 and 3.2.73-2+deb7u1 of it.  Changing nothing
> else, the jfs module loads and jfs partitions mount at boot with the earlier package
> version, and with the latest package the jfs module fails to load and dmesg contains
> those errors I mentioned.  Reproducable every time here, as I've switched the package 
> between versions several times (rebooting after each) to confirm.

Which boot loader are you using?  Your report doesn't list any:

Versions of packages linux-image-3.2.0-4-686-pae suggests:
pn  debian-kernel-handbook     <none>
pn  grub-pc | extlinux | lilo  <none>
ii  linux-doc-3.2              3.2.73-2+deb7u1

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'

[toc] | [prev] | [next] | [standalone]

#51796

On Fri, Dec 18, 2015 at 01:20:16PM +0000, Ben Hutchings wrote:

> 
> Which boot loader are you using?  Your report doesn't list any:
> 
> Versions of packages linux-image-3.2.0-4-686-pae suggests:
> pn  debian-kernel-handbook     <none>
> pn  grub-pc | extlinux | lilo  <none>
> ii  linux-doc-3.2              3.2.73-2+deb7u1

grub-legacy

grub v2 had some issue detecting my raid configuration years back so I stuck
with the older grub.  never investigated if the issue I ran into with it
was fixed, but since the old grub was meeting my needs I continued using it. 

[toc] | [prev] | [next] | [standalone]

#51797

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2015-12-18 at 08:29 -0500, Robert Henney wrote:
> On Fri, Dec 18, 2015 at 01:20:16PM +0000, Ben Hutchings wrote:
> 
> > 
> > Which boot loader are you using?  Your report doesn't list any:
> > 
> > Versions of packages linux-image-3.2.0-4-686-pae suggests:
> > pn  debian-kernel-handbook     
> > pn  grub-pc | extlinux | lilo  
> > ii  linux-doc-3.2              3.2.73-2+deb7u1
> 
> grub-legacy
> 
> grub v2 had some issue detecting my raid configuration years back so I stuck
> with the older grub.  never investigated if the issue I ran into with it
> was fixed, but since the old grub was meeting my needs I continued using it. 

Well it doesn't seem to be doing the right thing any more.  The error
messages you got indicate that the old kernel is being used with new
modules, i.e. the boot loader is not loading the upgraded kernel.
Please check the grub configuration.

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'

[toc] | [prev] | [next] | [standalone]

#51798

On Fri, Dec 18, 2015 at 01:34:28PM +0000, Ben Hutchings wrote:

> 
> Well it doesn't seem to be doing the right thing any more.  The error
> messages you got indicate that the old kernel is being used with new
> modules, i.e. the boot loader is not loading the upgraded kernel.
> Please check the grub configuration.

The grub configuration looks alright, and basically untouched from 
defaults.  But what you said about looking as if old modules were
being loaded got me thinking, so I recreated the initramfs image..

  update-initramfs -d -k 3.2.0-4-686-pae
  update-initramfs -c -k 3.2.0-4-686-pae

and now jfs is working.  So that means that the new kernel build 
isn't the problem as I had believed.

Not sure why the normal package upgrade process wasn't creating/updating 
the initramfs image properly, but it could certainly be grub-legacy
at fault, if it isn't due to something unique about this particular 
system's configuration (it's been dist-upgraded many times, starting
as etch or sarge).

This bug report can be closed.  If I find time to do some more 
investigation later and determine grub-legacy to be the actual culprit 
I'll file a bug report against that package.

[toc] | [prev] | [next] | [standalone]

#51791 — Processed: Re: Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update

Processing control commands:

> tag -1 moreinfo
Bug #808266 [src:linux] linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update
Added tag(s) moreinfo.

-- 
808266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808266
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#51926 — Bug#808266: marked as done (linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 28 Dec 2015 08:46:23 +0100
with message-id <20151228074623.GA9531@eldamar.local>
and subject line Re: Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update
has caused the Debian Bug report #808266,
regarding linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
808266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808266
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web