Bug#866122: kernel resolution
Thank you Barry (and Gustavo) for providing closure on this one. :) On Thu, Sep 12, 2019 at 04:18:00PM -0500, Barry Arndt wrote: One of the problems was introduced in 4.12, and the other in 4.15. For posterity I should note that I first encountered the issue back in 4.9 and bisected it to dc16b553c949e81f37555777dc7bab66d78285a7. It looks like the first commit you mentioned largely undoes that one. In any case I confirmed that cherry-picking those two patches on to an affected kernel does fix the issue for me. Thank you!
Bug#919706: RM: linux-signed/experimental -- obsolete
Package: ftp.debian.org Severity: normal I noticed that #915367 was closed by removing one binary package from experimental. However, the source package linux-signed/5 and the rest of its binaries are still there. linux-signed was removed from unstable in 2017 (#862902). Please consider removing it from experimental as well. Maintainers are CCed for their input.
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Control: found -1 4.17.3-1 Hi, On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: However it looks like it might be resolved with the kernel in unstable. I will run some more iterations and let you know. The issue still reproduces with stretch userland and the current unstable kernel. It cannot be reproduced with buster's glibc because lock elision was disabled in #878071, citing this issue. Thanks Ryan
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Control: found -1 4.9.88-1+deb9u1 Hi, On Sun, Jul 01, 2018 at 03:42:12AM +0100, Ben Hutchings wrote: Is this bug still present? It still reproduces with the current stretch kernel: debian@debian:~/openldap-2.4.44+dfsg/debian/build/tests$ ./run -b mdb test060-mt-hot Cleaning up test run directory leftover from previous run. Running ../../../tests/scripts/test060-mt-hot for mdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... Starting slapd on TCP/IP port 9011... /home/debian/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd -s0 -f /home/debian/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h ldap://localhost:9011/ -d stats Testing basic monitor search... Monitor searches Testing basic mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 1 -L 1 -l 5 Testing basic mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 5 -L 1 -l 1 Testing basic mt-hot search: 100 threads (5 x 100) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 100 -L 5 -l 100 Random searches Testing random mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5 Testing random mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1 slapd-mtread failed (139)! debian@debian:~/openldap-2.4.44+dfsg/debian/build/tests$ uname -a Linux debian 4.9.0-6-powerpc64le #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) ppc64le GNU/Linux However it looks like it might be resolved with the kernel in unstable. I will run some more iterations and let you know. a7771176 (4.15) looks interesting - it's specifically tagged as fixing the commit I isolated as the broken one (dc16b553), and the message sounds relevant. If the unstable kernel survives multiple runs I'll see what this does on 4.9. https://patchwork.ozlabs.org/patch/833190/
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
On Sun, Jul 01, 2018 at 03:42:12AM +0100, Ben Hutchings wrote: Is this bug still present? Thanks for the ping. The Unicamp Minicloud, where I was granted access to a VM for testing, is currently down for maintenance until July 7. I will check this again after it comes back.
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid
Control: tag -1 upstream
Hi Breno,
Today I built Linux 4.12 from upstream source and the test program still
crashes. I was looking at your fixes to initialize load_{fp,tm,vec} as
well as someone else fixing the CONFIG_ALIVEC typo but none of those
have helped.
I did confirm on this kernel that reverting 613036d9 still stops it from
crashing. Tomorrow I will try to narrow it down to a specific change.
There are only 4 hunks after all (the addition of msr_tm_active cannot
be reverted as there are more calls to it now).
It turns out it is _not_ compiler dependent. The test program compiled
in a jessie chroot succeeds in that chroot and then crashes if I run the
same binary in a stretch chroot. This also means I was wrong about the
m{t,f}vsrd instructions being related, as gcc-4.9 doesn't emit them (for
this particular program, at least).
On Mon, Jul 10, 2017 at 10:23:40AM -0300, Breno Leitao wrote:
Anyway, this is what I am going to investigate now:
1) If glibc's pthread method is using hardware transactional memory by
default. I remember that upstream enabled it once and then disabled by
default.
objdump -d libpthread.so.0 output apparently lists some tbegin/tend
instructions, but I suppose those could be selected at runtime?
Thanks
Ryan
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
Control: tag -1 patch On Sat, Nov 26, 2016 at 12:59:21PM -0800, Ryan Tandy wrote: Unfortunately dmesg and kern.log are flooded with messages like: [ 161.781360] Bad eraseblock 32764 at 0x0001fff0 [ 161.786261] Bad eraseblock 32765 at 0x0001fff4 [ 161.791159] Bad eraseblock 32766 at 0x0001fff8 [ 161.796058] Bad eraseblock 32767 at 0x0001fffc and boot takes a very long time due to logging all these messages. I suppose that's a side-effect of using the kurobox-pro dtb - guessing it has a different flash layout? Looks like that was the case. I applied your patch to orion5x-linkstation-lsgl.dts, rebuilt the dtb, dropped it into /etc/flash-kernel/dtbs, and ran flash-kernel again. Much better: [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.8.0-1-marvell (debian-kernel@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 Debian 4.8.5-1 (2016-10-28) [0.00] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a005317f [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] OF: fdt:Machine model: Buffalo Linkstation Pro/Live [...] [3.297636] sata_mv sata_mv.0: version 1.28 [3.297844] sata_mv sata_mv.0: cannot get optional clkdev [3.320803] sata_mv sata_mv.0: slots 32 ports 2 [3.386495] scsi host0: sata_mv [3.403996] scsi host1: sata_mv [3.411527] ata1: SATA max UDMA/133 irq 28 [3.415723] ata2: SATA max UDMA/133 irq 28 [3.733937] ata1: SATA link down (SStatus 0 SControl 300) [4.212767] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [4.241078] ata2.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7 [4.247154] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32) [4.293102] ata2.00: configured for UDMA/133 [4.298609] scsi 1:0:0:0: Direct-Access ATA SAMSUNG SP2504C 0-41 PQ: 0 ANSI: 5 [4.402529] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB) [4.416368] sd 1:0:0:0: [sda] Write Protect is off [4.421270] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.421705] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.474159] sda: sda1 sda2 sda3 < sda5 > [4.493519] sd 1:0:0:0: [sda] Attached SCSI disk
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
On Sun, Nov 27, 2016 at 01:20:10AM +0900, Roger Shimizu wrote: - start your device by kernel 4.3 first. - confirm your have flash-kernel and linux-image-4.8.0-1-marvell installed. - cp /usr/lib/linux-image-4.8.0-1-marvell/orion5x-kuroboxpro.dtb /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb - flash-kernel --force 4.8.0-1-marvell ~ # chroot /target flash-kernel --force 4.8.0-1-marvell DTB: orion5x-linkstation-lsgl.dtb Installing /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb into /boot/dtbs/4.8.0-1-marvell/orion5x-linkstation-lsgl.dtb Taking backup of orion5x-linkstation-lsgl.dtb. Installing new orion5x-linkstation-lsgl.dtb. Installing /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb into /boot/dtbs/4.8.0-1-marvell/orion5x-linkstation-lsgl.dtb Taking backup of orion5x-linkstation-lsgl.dtb. Installing new orion5x-linkstation-lsgl.dtb. flash-kernel: installing version 4.8.0-1-marvell flash-kernel: appending /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb to kernel Generating kernel u-boot image... done. Taking backup of uImage.buffalo. Installing new uImage.buffalo. Generating initramfs u-boot image... done. Taking backup of initrd.buffalo. Installing new initrd.buffalo. - check the log of above command, it should use /etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb for building uImage.buffalo, the kernel image for booting - reboot and see the result If the above steps works for you, I can submit the above patch to kernel upstream, and include it into Stretch release. So I'm looking forward to your result. Thank you! It booted! :) Linux xenon 4.8.0-1-marvell #1 Debian 4.8.5-1 (2016-10-28) armv5tel GNU/Linux Unfortunately dmesg and kern.log are flooded with messages like: [ 161.781360] Bad eraseblock 32764 at 0x0001fff0 [ 161.786261] Bad eraseblock 32765 at 0x0001fff4 [ 161.791159] Bad eraseblock 32766 at 0x0001fff8 [ 161.796058] Bad eraseblock 32767 at 0x0001fffc and boot takes a very long time due to logging all these messages. I suppose that's a side-effect of using the kurobox-pro dtb - guessing it has a different flash layout? Anyway, the change to nr-ports=2 looks good! Tested-by: Ryan Tandy Thanks!
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
On Fri, Nov 25, 2016 at 05:02:06PM +, Ian Campbell wrote: Oh, so the issue is not that you are missing a second disk, but rather that the one disk you do have seems to not be detected? You theory is that it is actually only the second port which is connected to anything in this hw? Yes, exactly.
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
On Fri, Nov 25, 2016 at 04:24:31PM +, Ian Campbell wrote: Is it possible that there are multiple variants of this one with differing numbers of disks? It's a little tricky to google for but all the LS-GL's I can see _look_ like they are single disk (see [*] below). Or maybe the naming is just confusing? I don't believe there is anything called LS-GL that supports more than one disk. Now that you mention it though, there are two hardware revisions out there: http://buffalo.nas-central.org/wiki/LinkstationProLiveDifferences I have the older (v1) hardware. I will crack the box open this weekend and confirm, but as far as I remember there was only one SATA connector. Aha, there was a guide for wiring up the second port, though: http://buffalo.nas-central.org/wiki/Add_a_Second_Hard_Drive_to_Your_LS_Pro_v1/LS_Live_v1 Mine has zero mods though, totally stock hardware-wise.
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
On Fri, Nov 25, 2016 at 07:42:37AM +, Ian Campbell wrote:
Assuming orion5x-linkstation.dtsi is correctly relating to your
platform you would appear to want one of:
$ git grep orion5x-linkstation.dtsi arch/arm/boot/dts/*.dts
arch/arm/boot/dts/orion5x-kuroboxpro.dts:#include "orion5x-linkstation.dtsi"
arch/arm/boot/dts/orion5x-linkstation-lsgl.dts:#include
"orion5x-linkstation.dtsi"
arch/arm/boot/dts/orion5x-linkstation-lswtgl.dts:#include
"orion5x-linkstation.dtsi"
(Or something else not yet present in the kernel tree.)
Mine is an LS-GL, so orion5x-linkstation-lsgl.dts should be the one.
(The model string in there is the same one I see at runtime, too.)
Of the three above orion5x-kuroboxpro.dts and orion5x-linkstation-
lswtgl both set ports to 2 using:
&sata {
nr-ports = <2>;
};
which overrides the defaults from the dtsi. You mentioned kurobox_pro-
setup.c so perhaps orion5x-kuroboxpro.dts is the one you want?
Exactly - orion5x-linkstation-lsgl.dts is missing this chunk. So my
suspicion is it needs the same override (or, if they all end up using
the same value, maybe the dtsi can change - Roger would know better than
I would). Sorry for the lack of clarity.
kurobox_pro-setup.c, AFAIK, used to be used on several related
platforms. The kurobox pro and LS-GL are nearly identical.
thanks
Ryan
Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)
Package: linux-image-4.8.0-1-marvell
Version: 4.8.7-1
Severity: normal
Tags: upstream
I found that on recent d-i images, the kernel does not detect the hard
drive on my LinkStation. I tried some older images and found that kernel
4.3.3-5 worked and kernel 4.6.2-2 did not.
I suspect the problem is with the device tree file, therefore CCing
Roger Shimizu who contributed that file.
The old kurobox_pro-setup.c contains this code:
static struct mv_sata_platform_data kurobox_pro_sata_data = {
.n_ports= 2,
};
whereas the new orion5x-linkstation.dtsi contains this code:
&sata {
status = "okay";
nr-ports = <1>;
};
The dmesg output seems to reinforce this conclusion.
dmesg from 4.3.0-1:
[ 611.914912] sata_mv sata_mv.0: version 1.28
[ 611.915107] sata_mv sata_mv.0: cannot get optional clkdev
[ 611.916086] sata_mv sata_mv.0: slots 32 ports 2
[ 611.971107] scsi host0: sata_mv
[ 611.984111] scsi host1: sata_mv
[ 611.984881] ata1: SATA max UDMA/133 irq 30
[ 611.984916] ata2: SATA max UDMA/133 irq 30
[ 612.302763] ata1: SATA link down (SStatus 0 SControl 300)
[ 612.778697] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 612.787074] ata2.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7
[ 612.787118] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 612.819082] ata2.00: configured for UDMA/133
[ 612.820339] scsi 1:0:0:0: Direct-Access ATA SAMSUNG SP2504C 0-41
PQ: 0 ANSI: 5
[ 612.899766] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232
GiB)
[ 612.900971] sd 1:0:0:0: [sda] Write Protect is off
[ 612.901031] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 612.901533] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 612.924886] sd 1:0:0:0: [sda] Attached SCSI disk
dmesg from 4.8.7-1:
[ 11.140091] sata_mv sata_mv.0: version 1.28
[ 11.140252] sata_mv sata_mv.0: cannot get optional clkdev
[ 11.170717] sata_mv sata_mv.0: slots 32 ports 1
[ 11.226581] scsi host0: sata_mv
[ 11.236985] ata1: SATA max UDMA/133 irq 28
[ 11.554565] ata1: SATA link down (SStatus 0 SControl 300)
In this extract, ata2 is apparently never scanned.
I expect changing nr-ports to 2 will fix this. I have not tested the
change yet, but will try to do so this weekend.
thanks
Ryan
Bug#590105: SATA drive not detected during squeeze installation on Buffalo LinkStation (squeeze
On 15/01/2011 2:37 PM, cvel...@gmail.com wrote: I'm also trying to install Squeeze on a LS-CHL (LS-C640L-EU) and can confirm, that it still does not recognise the sata drive. I don't have this hardware and I'm not at all familiar with the relevant kernel code, so I'm afraid there isn't anything I can do to help you with it. I don't know whether LS-CHL is even supported by kernel.org kernels yet. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d323735.4030...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
On 18/09/2010 2:10 PM, Ryan Tandy wrote: Sorry, please ignore this; I had forgotten to run flash-kernel. -21 does NOT work for me, even with ipv6.disable=1. Same behaviour with -22. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c952dc0.1020...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
On 18/09/2010 2:16 PM, Martin Michlmayr wrote: And you don't have a serial console you can connect to this machine? I don't. I can only interact with it over the network, and by attaching the drive to another computer. Since you say that you can run commands via /etc/rc.local, you're saying that the machines boots alright (just without bringing up the network)? That's correct. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c952c7e.2010...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
On 18/09/2010 2:07 PM, Ryan Tandy wrote: Seems that it might be. -21 works for me using the workaround suggested in that bug (ipv6.disable=1) Sorry, please ignore this; I had forgotten to run flash-kernel. -21 does NOT work for me, even with ipv6.disable=1. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c952aca.6070...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
On 18/09/2010 1:48 PM, Martin Michlmayr wrote: I wonder if this is the same as #597302, which was just reported. Seems that it might be. -21 works for me using the workaround suggested in that bug (ipv6.disable=1) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c952a16.6040...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
Hi Martin, Thanks for the quick response. Aren't you supposed to be on vacation? On 15/09/2010 1:55 AM, Martin Michlmayr wrote: Can you connect a serial console to see what's going on? Can you try 2.6.32-20 from http://snapshot.debian.org/ to see if that works? I don't see any network related changes between -20 and -21. I installed 2.6.32-20 and verified that it does work. I don't have serial access, but I can run commands using /etc/rc.local. thanks, Ryan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c9167bd.3070...@gmail.com
Bug#596924: orion5x kernel 2.6.32-21 fails to detect network link on Linkstation Pro
Package: linux-image-2.6.32-5-orion5x Version: 2.6.32-21 Severity: important Hi, Today I performed a network-console install of Squeeze on my Linkstation Pro, using a recent d-i from p.d.o/~joeyh. The installation completed successfully. Afterwards the system appeared to boot, but did not respond to ping. I attached the hard drive to another machine and discovered from the saved dmesg that the network device never entered the "link up" state. This appears to be a regression in 2.6.32-21 since the 2.6.32-20 kernel included in the installer works correctly. I'm attaching /var/log/dmesg from the not-working kernel. Please let me know if I can supply any additional information. thanks, Ryan [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-orion5x (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 Thu Aug 26 08:07:14 UTC 2010 [0.00] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: Buffalo Linkstation Pro/Live [0.00] Clearing invalid memory bank 0...@0x [0.00] Clearing invalid memory bank 0...@0x [0.00] Clearing invalid memory bank 0...@0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x [0.00] Ignoring unrecognised tag 0x41000403 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c038a218, node_mem_map c03f3000 [0.00] Normal zone: 256 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 32512 pages, LIFO batch:7 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: root=/dev/sda2 ro [0.00] PID hash table entries: 512 (order: -1, 2048 bytes) [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Memory: 128MB = 128MB total [0.00] Memory: 123432KB available (3220K code, 573K data, 128K init, 0K highmem) [0.00] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] NR_IRQS:64 [0.00] Console: colour dummy device 80x30 [0.00] console [tty0] enabled [ 25.770741] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) [ 26.009983] Security Framework initialized [ 26.010059] SELinux: Disabled at boot. [ 26.010150] Mount-cache hash table entries: 512 [ 26.010878] Initializing cgroup subsys ns [ 26.010950] Initializing cgroup subsys cpuacct [ 26.011012] Initializing cgroup subsys devices [ 26.011073] Initializing cgroup subsys freezer [ 26.011132] Initializing cgroup subsys net_cls [ 26.011267] CPU: Testing write buffer coherency: ok [ 26.012922] devtmpfs: initialized [ 26.016398] regulator: core version 0.5 [ 26.016910] NET: Registered protocol family 16 [ 26.018144] Orion ID: MV88F5182-A2. TCLK=16667. [ 26.023906] bio: create slab at 0 [ 26.024784] vgaarb: loaded [ 26.026535] Switching to clocksource orion_clocksource [ 26.039073] NET: Registered protocol family 2 [ 26.039781] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 26.041957] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 26.042272] TCP bind hash table entries: 4096 (order: 2, 16384 bytes) [ 26.042453] TCP: Hash tables configured (established 4096 bind 4096) [ 26.042520] TCP reno registered [ 26.043010] NET: Registered protocol family 1 [ 26.043520] Unpacking initramfs... [ 26.503725] Freeing initrd memory: 2328K [ 26.503966] NetWinder Floating Point Emulator V0.97 (double precision) [ 26.504798] audit: initializing netlink socket (disabled) [ 26.504924] type=2000 audit(0.720:1): initialized [ 26.527011] VFS: Disk quotas dquot_6.5.2 [ 26.527865] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 26.528265] msgmni has been set to 245 [ 26.530126] alg: No test for stdrng (krng) [ 26.530501] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 26.530605] io scheduler noop registered [ 26.530661] io scheduler anticipatory registered [ 26.530721] io scheduler deadline registered [ 26.531414] io scheduler cfq registered (default) [ 26.549491] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 26.550822] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A [ 26.551595] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A [ 26.552713] physmap platform flash device: 0004 at f400 [ 26.552971] Found: SST 39LF020 [ 26.553060
Bug#588164: linux-image-2.6.32-5-orion5x: kernel NULL pointer dereference while loading module parport_pc
Package: linux-2.6 Version: 2.6.32-15 Severity: normal A kernel oops was generated while restarting cups as part of today's aptitude upgrade. The oops is reproducible and occurs at each boot, apparently while loading parport_pc as requested by /etc/init.d/cups. My printer is a USB printer and has been off the whole time. 2.6.33-2-orion5x from experimental exhibits the same oops (hence the appearance of experimental in a couple of package versions below). I've attached an excerpt from dpkg.log to show which packages were updated before the oops started happening. I'm not familiar with reporting kernel bugs so please let me know if I can provide additional information. -- Package-specific info: ** Version: Linux version 2.6.32-5-orion5x (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 Fri Jun 4 11:47:35 UTC 2010 ** Command line: root=/dev/sda2 ro ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 26.650873] VFP support v0.3: not present [ 26.651762] registered taskstats version 1 [ 26.653704] rtc-rs5c372 0-0032: setting system clock to 2010-07-05 17:17:27 UTC (1278350247) [ 26.653844] Initalizing network drop monitor service [ 26.654085] Freeing init memory: 120K [ 26.857810] udev: starting version 158 [ 27.790004] SCSI subsystem initialized [ 28.245090] libata version 3.00 loaded. [ 28.351304] sata_mv sata_mv.0: version 1.28 [ 28.352406] sata_mv sata_mv.0: slots 32 ports 2 [ 28.354203] scsi0 : sata_mv [ 28.356231] scsi1 : sata_mv [ 28.357927] ata1: SATA max UDMA/133 irq 29 [ 28.358011] ata2: SATA max UDMA/133 irq 29 [ 28.707192] ata1: SATA link down (SStatus 0 SControl 300) [ 29.217196] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 29.237541] ata2.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7 [ 29.237638] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 29.277708] ata2.00: configured for UDMA/133 [ 29.278521] scsi 1:0:0:0: Direct-Access ATA SAMSUNG SP2504C VT10 PQ: 0 ANSI: 5 [ 29.422678] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB) [ 29.423707] sd 1:0:0:0: [sda] Write Protect is off [ 29.423792] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 29.424205] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 29.428571] sda: sda1 sda2 sda3 < sda5 > [ 29.472483] sd 1:0:0:0: [sda] Attached SCSI disk [ 30.440552] kjournald starting. Commit interval 5 seconds [ 30.440690] EXT3-fs: mounted filesystem with ordered data mode. [ 32.241266] udev: starting version 158 [ 33.678767] MV-643xx 10/100/1000 ethernet driver version 1.4 [ 33.679587] mv643xx_eth smi: probed [ 33.743194] net eth0: port 0 with MAC address 00:16:01:41:82:92 [ 34.187568] usbcore: registered new interface driver usbfs [ 34.190750] usbcore: registered new interface driver hub [ 34.193566] usbcore: registered new device driver usb [ 34.299007] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 34.299238] orion-ehci orion-ehci.0: Marvell Orion EHCI [ 34.299474] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 34.327255] orion-ehci orion-ehci.0: irq 17, io mem 0xf105 [ 34.347242] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 34.347488] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 34.347573] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 34.347665] usb usb1: Product: Marvell Orion EHCI [ 34.347729] usb usb1: Manufacturer: Linux 2.6.32-5-orion5x ehci_hcd [ 34.347801] usb usb1: SerialNumber: orion-ehci.0 [ 34.357297] usb usb1: configuration #1 chosen from 1 choice [ 34.358905] hub 1-0:1.0: USB hub found [ 34.359075] hub 1-0:1.0: 1 port detected [ 34.359601] orion-ehci orion-ehci.1: Marvell Orion EHCI [ 34.359752] orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2 [ 34.387270] orion-ehci orion-ehci.1: irq 12, io mem 0xf10a [ 34.407240] orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00 [ 34.407499] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 34.407585] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 34.407677] usb usb2: Product: Marvell Orion EHCI [ 34.407742] usb usb2: Manufacturer: Linux 2.6.32-5-orion5x ehci_hcd [ 34.407816] usb usb2: SerialNumber: orion-ehci.1 [ 34.409368] usb usb2: configuration #1 chosen from 1 choice [ 34.410467] hub 2-0:1.0: USB hub found [ 34.411835] hub 2-0:1.0: 1 port detected [ 35.524346] Adding 368632k swap on /dev/sda5. Priority:-1 extents:1 across:368632k [ 36.404484] EXT3 FS on sda2, internal journal [ 36.956102] loop: module loaded [ 42.700428] eth0: link up, 1000 Mb/s, full duplex, flow control disabled [ 45.224294] NET: Registered protocol family 10 [ 45.239864] lo: Disabled Privacy Extensions [ 46.417379] Unable to handle kernel NULL pointer dereference at virtual address 000
Bug#517771: USB_HIDDEV also needed in 2.6.28
Please also enable this option in the 2.6.28 orion5x kernel. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
