http://bugzilla.novell.com/show_bug.cgi?id=509449 Summary: blkext grabs hdd devices, stuff doesn't work Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jslaby@novell.com QAContact: qa@suse.de CC: xwhu@novell.com, seife@novell.com, knikanth@novell.com, rjw@novell.com Found By: --- After updating master kotd from 6580dd3e9ae59976b902a43cb1407cc863f22b9e to d2da64bc36fbbe03123416ec036321abbfa98daf my machine got almost unusable. $ cat /sys/block/sda/sda?/dev 259:1 259:2 259:3 259:4 259:5 259:6 259:7 259:8 it got exposed by $ grep 259 /proc/devices 259 blkext suspend (and kernel/power/user.c) doesn't count with majors > 255. lvm (lvm2-2.02.45-6.1) won't activate lvm until I change its proc conf to something meaningless (/hole), since it ignores blkext entries otherwise. Is this expected behaviour? Then userspace should be fixed. If not, what could have caused this? I see nothing related in the kernel changelog, so I doubt it's bound directly with the kernel update. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.